This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Make fprintf() function to multithread-safe

From: Andreas Schwab <schwab at linux-m68k dot org>
To: Peng Haitao <penght at cn dot fujitsu dot com>
Cc: drepper at gmail dot com, libc-alpha at sourceware dot org
Date: Wed, 20 Jun 2012 10:17:31 +0200
Subject: Re: [PATCH] Make fprintf() function to multithread-safe
References: <1340170889-3498-1-git-send-email-penght@cn.fujitsu.com><m2txy6mpdx.fsf@igel.home> <4FE17BA8.7000902@cn.fujitsu.com>

Peng Haitao <penght@cn.fujitsu.com> writes:

> I think use two locks will be better. because __printf_va_arg_table and __printf_function_table
> can be modified simultaneously when use two locks.

This is in no way performance critical.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Follow-Ups:
- [PATCH v2] Make fprintf() function to multithread-safe
  - From: Peng Haitao

References:
- [PATCH] Make fprintf() function to multithread-safe
  - From: Peng Haitao
- Re: [PATCH] Make fprintf() function to multithread-safe
  - From: Andreas Schwab
- Re: [PATCH] Make fprintf() function to multithread-safe
  - From: Peng Haitao

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]