From: "Sven Köhler" <skoehler@upb.de>
To: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
stian@nixia.no, Blaisorblade <blaisorblade_spam@yahoo.it>,
User-mode Linux Kernel Development
<user-mode-linux-devel@lists.sourceforge.net>,
Jeff Dike <jdike@addtoit.com>, Roland Kaeser <roli8200@yahoo.de>,
Nuno Silva <nuno.silva@vgertech.com>,
Antoine Martin <antoine@nagafix.co.uk>,
Dennis Muhlestein <devel@muhlesteins.com>
Subject: Re: [uml-devel] Re: Stop at startup on 2.6 NPTL hosts
Date: Wed, 10 Nov 2004 15:44:21 +0100 [thread overview]
Message-ID: <41922945.2090805@upb.de> (raw)
In-Reply-To: <41920646.3090802@fujitsu-siemens.com>
>> If you want to be 100% sure you use a syscall, why not call the syscall
>> directly?
>
> OK. It's an API call. But what's this API call defined to return? Isn't
> it the
> pid of the process calling? If it is, the behavior of the lib is a bug.
> If it
> isn't, the descriptions are wrong. Do you agree?
This glibc-Bug has been discussed on the LKML already. Linus was
somewhat angry about it, since glibc should not cache. He said that this
caching-stuff may be, because somewhat wanted to tune glibc for some
synthetic benchmark that uses getpid() as a speed measurement. He also
recommed to get rid of that cache - at least as far as i read the
discussion.
So the conclusion is: override getpid() with something that does not
cache anything since there are buggy glibc's out there, or use our own
cache for the PID if syscalls cause to much overhead.
Thx
Sven
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-11-10 14:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 9:26 [uml-devel] UML Kernel 2.6.7 Nothing happens Roland Kaeser
2004-11-02 18:52 ` Stop at startup on 2.6 NPTL hosts (was: Re: [uml-devel] UML Kernel 2.6.7 Nothing happens) Blaisorblade
2004-11-02 23:43 ` [uml-devel] Re: Stop at startup on 2.6 NPTL hosts Sven Köhler
2004-11-03 3:04 ` Nuno Silva
2004-11-03 8:32 ` Gerd Knorr
2004-11-03 15:59 ` Blaisorblade
2004-11-03 20:10 ` Gerd Knorr
2004-11-03 22:17 ` Blaisorblade
2004-11-03 22:17 ` Blaisorblade
2004-11-04 8:40 ` Nuno Silva
2004-11-09 16:42 ` Bodo Stroesser
2004-11-09 17:29 ` Adam Heath
2004-11-09 17:32 ` Bodo Stroesser
2004-11-09 18:23 ` Bodo Stroesser
2004-11-09 19:11 ` Blaisorblade
2004-11-10 8:36 ` stian
2004-11-10 9:07 ` Geert Uytterhoeven
2004-11-10 12:15 ` Bodo Stroesser
2004-11-10 12:47 ` Geert Uytterhoeven
2004-11-10 14:32 ` Blaisorblade
2004-11-10 14:44 ` Sven Köhler [this message]
2004-11-10 21:19 ` Henrik Nordstrom
2004-11-15 17:17 ` Blaisorblade
2004-11-10 17:16 ` Blaisorblade
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41922945.2090805@upb.de \
--to=skoehler@upb.de \
--cc=antoine@nagafix.co.uk \
--cc=blaisorblade_spam@yahoo.it \
--cc=bstroesser@fujitsu-siemens.com \
--cc=devel@muhlesteins.com \
--cc=geert@linux-m68k.org \
--cc=jdike@addtoit.com \
--cc=nuno.silva@vgertech.com \
--cc=roli8200@yahoo.de \
--cc=stian@nixia.no \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.