From: Andi Kleen <ak@suse.de>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sys_sched_yield fast path
Date: 10 Mar 2001 17:59:33 +0100 [thread overview]
Message-ID: <oup4rx1tv9m.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <XFMail.20010310123041.davidel@xmailserver.org>
In-Reply-To: Davide Libenzi's message of "10 Mar 2001 11:23:39 +0100"
Davide Libenzi <davidel@xmailserver.org> writes:
> Probably the rate at which is called sys_sched_yield() is not so high to let
> the performance improvement to be measurable.
LinuxThreads mutexes call sched_yield() when a lock is locked, so when you
have a multithreaded program with some lock contention it'll be called a lot.
-Andi
next prev parent reply other threads:[~2001-03-10 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-10 0:47 sys_sched_yield fast path Mike Kravetz
2001-03-10 11:30 ` Davide Libenzi
2001-03-10 16:59 ` Andi Kleen [this message]
2001-03-11 14:12 ` Davide Libenzi
2001-03-11 13:54 ` Anton Blanchard
2001-03-11 19:17 ` Dave Zarzycki
2001-03-12 0:18 ` Davide Libenzi
2001-03-11 23:46 ` Davide Libenzi
2001-03-12 0:10 ` Davide Libenzi
2001-03-12 1:24 ` Anton Blanchard
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=oup4rx1tv9m.fsf@pigdrop.muc.suse.de \
--to=ak@suse.de \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
/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