From: Peter Waechtler <pwaechtler@mac.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jamie Lokier <jamie@shareable.org>,
Ulrich Drepper <drepper@redhat.com>,
Krzysztof Benedyczak <golbi@mat.uni.torun.pl>,
linux-kernel@vger.kernel.org,
Manfred Spraul <manfred@colorfullife.com>,
Michal Wronski <wrona@mat.uni.torun.pl>
Subject: Re: POSIX message queues
Date: Tue, 07 Oct 2003 09:50:16 +0200 [thread overview]
Message-ID: <1448383.1065513016965.JavaMail.pwaechtler@mac.com> (raw)
On Sunday, October 05, 2003, at 08:32PM, Jakub Jelinek <jakub@redhat.com> wrote:
>> Speaking of librt - I should not have to link in pthreads and the
>> run-time overhead associated with it (locking stdio etc.) just so I
>> can use shm_open(). Any chance of fixing this?
>
>That overhead is mostly gone in current glibcs (when using NPTL):
>a) e.g. locking is done unconditionally even when libpthread is not present
> (it is just lock cmpxchgl, inlined)
a "lock cmpxchg" is > 100 cycles (according to a recent Linux Journal article
from Paul McKenney: 107ns on 700MHz PentiumIII)
But I think you will have benchmarked the alternatives?
BTW, what are they?
you suggested naming the syscall number symbols NR_mq_open instead of
NR_sys_mq_open. In the stub I want to overload some syscalls (e.g. mq_open)
but others not (e.g. mq_timedsend).
How to deal with that?
next reply other threads:[~2003-10-07 7:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 7:50 Peter Waechtler [this message]
2003-10-07 8:11 ` POSIX message queues Jakub Jelinek
-- strict thread matches above, loose matches on Subject: below --
2003-10-05 9:13 Krzysztof Benedyczak
2003-10-05 10:11 ` Manfred Spraul
2003-10-06 19:04 ` Krzysztof Benedyczak
2003-10-05 16:35 ` Ulrich Drepper
2003-10-05 18:16 ` Jamie Lokier
2003-10-05 18:32 ` Jakub Jelinek
2003-10-05 19:18 ` Jamie Lokier
2003-10-05 21:52 ` Ulrich Drepper
2002-10-02 10:35 Krzysztof Benedyczak
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=1448383.1065513016965.JavaMail.pwaechtler@mac.com \
--to=pwaechtler@mac.com \
--cc=drepper@redhat.com \
--cc=golbi@mat.uni.torun.pl \
--cc=jakub@redhat.com \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=wrona@mat.uni.torun.pl \
/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 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 NNTP newsgroup(s).