This is the mail archive of the glibc-bugs@sources.redhat.com 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]

[Bug libc/1005] putc() runs slower


------- Additional Comments From uttamp at us dot ibm dot com  2005-07-11 17:46 -------
Created an attachment (id=551)
 --> (http://sources.redhat.com/bugzilla/attachment.cgi?id=551&action=view)
proposed libio-stream lock/unlock patch

patch has added a check in _IO_putc(), _IO_getc(), putchar() and getchar()
library call if the calling app is single threaded or not. If it is single
threaded at the time of call to any of the above call, then call unlocked
version of library functions. This make sense because, when an application (
not multithreaded) calls putc() or any of the above call, thread of executation
is going to remain single, till we come back from the call and execute
pthread_create() and so on. There is no chance of new thread getting created
while application is in any of the above mentioned call. I've built and ran
complete glibc testsuite with the above patch and did not see any new failures
but saw an improvement in the performance numbers (obviously).


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #516 is|0                           |1
           obsolete|                            |


http://sources.redhat.com/bugzilla/show_bug.cgi?id=1005

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


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