public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: linux-arch@vger.kernel.org, mingo@elte.hu, paulus@samba.org
Subject: Re: [patch 0/3] Directed yield.
Date: Mon, 18 Sep 2006 10:53:50 -0700	[thread overview]
Message-ID: <20060918105350.25f02252.akpm@osdl.org> (raw)
In-Reply-To: <20060918121959.GA3290@skybase>

On Mon, 18 Sep 2006 14:19:59 +0200
Martin Schwidefsky <schwidefsky@de.ibm.com> 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?

Thanks.

      reply	other threads:[~2006-09-18 17:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-18 12:19 [patch 0/3] Directed yield Martin Schwidefsky
2006-09-18 17:53 ` Andrew Morton [this message]

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=20060918105350.25f02252.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=schwidefsky@de.ibm.com \
    /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