From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, akpm@osdl.org
Cc: mingo@elte.hu, paulus@samba.org
Subject: [patch 0/3] Directed yield take 3.
Date: Tue, 19 Sep 2006 13:19:17 +0200 [thread overview]
Message-ID: <20060919111917.GB21713@skybase> (raw)
On Mon, 2006-09-18 at 10:53 -0700, Andrew Morton wrote:
> > nobody has complained about my spinlock yield patches.
>
> Complain.
>
> I had to hunt around a bit to discover that this functionality has
> something to do with "giving up the timeslice of a virtual cpu in favour of
> a specific cpu". And also that it is expected to be of some
> briefly-alluded-to benefit on powerpc.
>
> So... Could you please flesh out the description/rationale rather a lot
> and cc linux-kernel on the patches?
Ok here we go,
added some more beef to the description of patch #1 and replaced the
description of patch #2. Good enough now?
--
blue skies,
Martin.
Martin Schwidefsky
Linux for zSeries Development & Services
IBM Deutschland Entwicklung GmbH
"Reality continues to ruin my life." - Calvin.
reply other threads:[~2006-09-19 11:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060919111917.GB21713@skybase \
--to=schwidefsky@de.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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