public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Marin Mitov <mitov@issp.bas.bg>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Subject: Re: is minimum udelay() not respected in preemptible SMP kernel-2.6.23?
Date: Wed, 7 Nov 2007 20:44:26 -0600	[thread overview]
Message-ID: <20071108024425.GR19691@waste.org> (raw)
In-Reply-To: <200711080220.59086.ak@suse.de>

On Thu, Nov 08, 2007 at 02:20:58AM +0100, Andi Kleen wrote:
> 
> > But I think we'd be best off stashing a single bit somewhere and
> > checking it at migrate time (relatively infrequent) rather than
> > copying and zeroing out a potentially enormous affinity mask every
> > time we disable migration (often, and in fast paths). Perhaps adding
> > TASK_PINNED to the task state flags would do it?
> 
> It would need to be a count to be able to nest it.

Ahh, right. Suppose that means fattening the task struct until someone
comes up with something more clever.

-- 
Mathematics is the supreme nostalgia of our time.

  reply	other threads:[~2007-11-08  2:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-07 17:21 is minimum udelay() not respected in preemptible SMP kernel-2.6.23? Marin Mitov
2007-11-07 20:30 ` Andrew Morton
2007-11-07 23:10   ` Andi Kleen
2007-11-08  0:20   ` Matt Mackall
2007-11-08  0:31     ` Andi Kleen
2007-11-08  1:03       ` Matt Mackall
2007-11-08  1:20         ` Andi Kleen
2007-11-08  2:44           ` Matt Mackall [this message]
2007-11-08 11:46       ` Avi Kivity
2007-11-08 15:10         ` Matt Mackall
2007-11-08  9:11     ` Peter Zijlstra
2007-11-08 15:43       ` Matt Mackall
2007-11-08 11:24   ` Marin Mitov

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=20071108024425.GR19691@waste.org \
    --to=mpm@selenic.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mitov@issp.bas.bg \
    --cc=tglx@linutronix.de \
    /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