summaryrefslogtreecommitdiff
path: root/FAQ.in
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>1999-03-01 07:21:39 +0000
committerUlrich Drepper <drepper@redhat.com>1999-03-01 07:21:39 +0000
commit9f6b6d8d19c17bdb5a30573c0ffc64e4177c7a49 (patch)
tree93278462f031ac5ae33061b1f236f11a85e4cb7f /FAQ.in
parent407a7d0eb770ae079a662e7b2b8cff5a750ca6ed (diff)
Update.
1999-03-01 Andreas Jaeger <aj@arthur.rhein-neckar.de> * sysdeps/i386/sys/ucontext.h (ucontext): Rename field uc_links to uc_link which is the right name according to Unix98. Reported by Craig Metz [PR libc/1001]. * sysdeps/arm/sys/ucontext.h (ucontext): Likewise. * sysdeps/m68k/sys/ucontext.h (ucontext): Likewise. * sysdeps/mips/sys/ucontext.h (ucontext): Likewise. * sysdeps/unix/sysv/linux/alpha/sys/ucontext.h (ucontext): Likewise. * sysdeps/unix/sysv/linux/i386/sys/ucontext.h (ucontext): Likewise * sysdeps/unix/sysv/linux/powerpc/sys/ucontext.h (ucontext): Likewise.
Diffstat (limited to 'FAQ.in')
-rw-r--r--FAQ.in9
1 files changed, 9 insertions, 0 deletions
diff --git a/FAQ.in b/FAQ.in
index 7a0d1a087d..495e30c6af 100644
--- a/FAQ.in
+++ b/FAQ.in
@@ -1278,6 +1278,15 @@ When compiling new programs against glibc 2.1, you've got to specify the
correct paths to the compiler (option -I with gcc) and linker (options
--dynamic-linker, -L and --rpath).
+? bonnie reports that char i/o with glibc 2 is much slower than with
+ libc5. What can be done?
+
+{AJ} The GNU C library uses thread safe functions by default and libc5 used
+non thread safe versions. The non thread safe functions have in glibc the
+suffix `_unlocked', for details check <stdio.h>. Using `putc_unlocked' etc.
+instead of `putc' should give nearly the same speed with bonnie (bonnie is a
+benchmark program for measuring disk access).
+
? Miscellaneous