From: Davide Libenzi <davidel@xmailserver.org>
To: Dave Zarzycki <dave@zarzycki.org>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>,
Anton Blanchard <anton@linuxcare.com.au>
Subject: Re: sys_sched_yield fast path
Date: Mon, 12 Mar 2001 01:18:36 +0100 (CET) [thread overview]
Message-ID: <XFMail.20010312011836.davidel@xmailserver.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0103111038420.9486-100000@batman.zarzycki.org>
On 11-Mar-2001 Dave Zarzycki wrote:
> On Mon, 12 Mar 2001, Anton Blanchard wrote:
>
>> Perhaps we need something like sched_yield that takes off some of
>> tsk->counter so the task with the spinlock will run earlier.
>
> Personally speaking, I wish sched_yield() API was like so:
>
> int sched_yield(pid_t pid);
Yes, You could do an API like this but it's not the mean of sched_yield().
> This would allow the thread wanting to acquire the spinlock to yield
> specifically to the thread holding the lock (assuming the pid of the lock
> holder was stored in the spinlock...) In fact, the the original lock owner
> could in theory yield back to the threading wanting to acquire the lock.
Everything happens inside a spinlock should be very fast otherwise the use of a
spinlock should be avoided.
- Davide
next prev parent reply other threads:[~2001-03-11 22:55 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
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 [this message]
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=XFMail.20010312011836.davidel@xmailserver.org \
--to=davidel@xmailserver.org \
--cc=ak@suse.de \
--cc=anton@linuxcare.com.au \
--cc=dave@zarzycki.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