public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/1005] New: putc() runs slower
@ 2005-06-10 21:37 uttamp at us dot ibm dot com
  2005-06-10 21:46 ` [Bug libc/1005] " uttamp at us dot ibm dot com
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: uttamp at us dot ibm dot com @ 2005-06-10 21:37 UTC (permalink / raw)
  To: glibc-bugs

Bonnie application runs slower with nptl configured glibc library. This
application calls putc() in a tight loop. While using nptl configured libc
(static or dynamic version), causes the worst runtime performance.

-- 
           Summary: putc() runs slower
           Product: glibc
           Version: 2.3.3
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: uttamp at us dot ibm dot com
                CC: glibc-bugs at sources dot redhat dot com,uttamp at us
                    dot ibm dot com
 GCC build triplet: powerpc-linux
  GCC host triplet: powerpc-linux
GCC target triplet: powerpc-linux


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.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libc/1005] putc() runs slower
  2005-06-10 21:37 [Bug libc/1005] New: putc() runs slower uttamp at us dot ibm dot com
@ 2005-06-10 21:46 ` uttamp at us dot ibm dot com
  2005-06-24 22:26 ` uttamp at us dot ibm dot com
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: uttamp at us dot ibm dot com @ 2005-06-10 21:46 UTC (permalink / raw)
  To: glibc-bugs


------- Additional Comments From uttamp at us dot ibm dot com  2005-06-10 21:46 -------
Created an attachment (id=516)
 --> (http://sources.redhat.com/bugzilla/attachment.cgi?id=516&action=view)
Proposed patch


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|gotom at debian dot or dot  |uttamp at us dot ibm dot com
                   |jp                          |
             Status|NEW                         |ASSIGNED


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.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libc/1005] putc() runs slower
  2005-06-10 21:37 [Bug libc/1005] New: putc() runs slower uttamp at us dot ibm dot com
  2005-06-10 21:46 ` [Bug libc/1005] " uttamp at us dot ibm dot com
@ 2005-06-24 22:26 ` uttamp at us dot ibm dot com
  2005-07-11 17:46 ` uttamp at us dot ibm dot com
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: uttamp at us dot ibm dot com @ 2005-06-24 22:26 UTC (permalink / raw)
  To: glibc-bugs


------- Additional Comments From uttamp at us dot ibm dot com  2005-06-24 22:25 -------
Can this patch be verified?

-- 


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.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libc/1005] putc() runs slower
  2005-06-10 21:37 [Bug libc/1005] New: putc() runs slower uttamp at us dot ibm dot com
  2005-06-10 21:46 ` [Bug libc/1005] " uttamp at us dot ibm dot com
  2005-06-24 22:26 ` uttamp at us dot ibm dot com
@ 2005-07-11 17:46 ` uttamp at us dot ibm dot com
  2005-09-23  2:35 ` drepper at redhat dot com
  2006-02-13 15:26 ` gsmith at us dot ibm dot com
  4 siblings, 0 replies; 6+ messages in thread
From: uttamp at us dot ibm dot com @ 2005-07-11 17:46 UTC (permalink / raw)
  To: glibc-bugs


------- 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.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libc/1005] putc() runs slower
  2005-06-10 21:37 [Bug libc/1005] New: putc() runs slower uttamp at us dot ibm dot com
                   ` (2 preceding siblings ...)
  2005-07-11 17:46 ` uttamp at us dot ibm dot com
@ 2005-09-23  2:35 ` drepper at redhat dot com
  2006-02-13 15:26 ` gsmith at us dot ibm dot com
  4 siblings, 0 replies; 6+ messages in thread
From: drepper at redhat dot com @ 2005-09-23  2:35 UTC (permalink / raw)
  To: glibc-bugs


------- Additional Comments From drepper at redhat dot com  2005-09-23 02:35 -------
This is why there is putc_unlocked.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |WONTFIX


http://sourceware.org/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.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug libc/1005] putc() runs slower
  2005-06-10 21:37 [Bug libc/1005] New: putc() runs slower uttamp at us dot ibm dot com
                   ` (3 preceding siblings ...)
  2005-09-23  2:35 ` drepper at redhat dot com
@ 2006-02-13 15:26 ` gsmith at us dot ibm dot com
  4 siblings, 0 replies; 6+ messages in thread
From: gsmith at us dot ibm dot com @ 2006-02-13 15:26 UTC (permalink / raw)
  To: glibc-bugs


------- Additional Comments From gsmith at us dot ibm dot com  2006-02-13 15:26 -------
(In reply to comment #4)
> This is why there is putc_unlocked.

We can't very well advise someone to substitute putc_unlocked() for putc().  
Suppose some sap did this, and then years later the code gets reused in a 
threaded application -- this well-intentioned advice could cause very hard-to-
find problems.

-- 


http://sourceware.org/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.


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2006-02-13 15:26 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-06-10 21:37 [Bug libc/1005] New: putc() runs slower uttamp at us dot ibm dot com
2005-06-10 21:46 ` [Bug libc/1005] " uttamp at us dot ibm dot com
2005-06-24 22:26 ` uttamp at us dot ibm dot com
2005-07-11 17:46 ` uttamp at us dot ibm dot com
2005-09-23  2:35 ` drepper at redhat dot com
2006-02-13 15:26 ` gsmith at us dot ibm dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).