All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: "Chen, Kenneth W" <kenneth.w.chen@intel.com>,
	Keith Owens <kaos@ocs.com.au>,
	David.Mosberger@acm.org, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: Add prefetch switch stack hook in scheduler function
Date: Fri, 29 Jul 2005 09:45:19 +0000	[thread overview]
Message-ID: <20050729094519.GA12975@elte.hu> (raw)
In-Reply-To: <20050729100257.A10345@flint.arm.linux.org.uk>


* Russell King <rmk+lkml@arm.linux.org.uk> wrote:

> On Fri, Jul 29, 2005 at 10:28:26AM +0200, Ingo Molnar wrote:
> > @@ -2872,10 +2878,10 @@ go_idle:
> >  	/*
> >  	 * Prefetch (at least) a cacheline below the current
> >  	 * kernel stack (in expectation of any new task touching
> > -	 * the stack at least minimally), and a cacheline above
> > -	 * the stack:
> > +	 * the stack at least minimally), and at least a cacheline
> > +	 * above the stack:
> >  	 */
> > -	prefetch_range(kernel_stack(next) - MIN_KERNEL_STACK_FOOTPRINT,
> > +	prefetch_range(kernel_stack(next) - L1_CACHE_BYTES,
> >  		       MIN_KERNEL_STACK_FOOTPRINT + L1_CACHE_BYTES);
> 
> This needs to ensure that we don't prefetch outside the page of the 
> kernel stack - otherwise we risk weird problems on architectures which 
> support prefetching but not DMA cache coherency.

ok, agreed. Since kernel_stack(next) defaults to 'next', we go below 
that structure which has unknown coherency attributes. I guess the 
easiest solution would be to default kernel_stack(next) to '(void *)next 
+ L1_CACHE_BYTES'? That way the default prefetching would happen for the 
[next...next+2*L1_BYTES] range.

	Ingo

WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: "Chen, Kenneth W" <kenneth.w.chen@intel.com>,
	Keith Owens <kaos@ocs.com.au>,
	David.Mosberger@acm.org, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: Add prefetch switch stack hook in scheduler function
Date: Fri, 29 Jul 2005 11:45:19 +0200	[thread overview]
Message-ID: <20050729094519.GA12975@elte.hu> (raw)
In-Reply-To: <20050729100257.A10345@flint.arm.linux.org.uk>


* Russell King <rmk+lkml@arm.linux.org.uk> wrote:

> On Fri, Jul 29, 2005 at 10:28:26AM +0200, Ingo Molnar wrote:
> > @@ -2872,10 +2878,10 @@ go_idle:
> >  	/*
> >  	 * Prefetch (at least) a cacheline below the current
> >  	 * kernel stack (in expectation of any new task touching
> > -	 * the stack at least minimally), and a cacheline above
> > -	 * the stack:
> > +	 * the stack at least minimally), and at least a cacheline
> > +	 * above the stack:
> >  	 */
> > -	prefetch_range(kernel_stack(next) - MIN_KERNEL_STACK_FOOTPRINT,
> > +	prefetch_range(kernel_stack(next) - L1_CACHE_BYTES,
> >  		       MIN_KERNEL_STACK_FOOTPRINT + L1_CACHE_BYTES);
> 
> This needs to ensure that we don't prefetch outside the page of the 
> kernel stack - otherwise we risk weird problems on architectures which 
> support prefetching but not DMA cache coherency.

ok, agreed. Since kernel_stack(next) defaults to 'next', we go below 
that structure which has unknown coherency attributes. I guess the 
easiest solution would be to default kernel_stack(next) to '(void *)next 
+ L1_CACHE_BYTES'? That way the default prefetching would happen for the 
[next...next+2*L1_BYTES] range.

	Ingo

  reply	other threads:[~2005-07-29  9:45 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-27 22:07 Add prefetch switch stack hook in scheduler function Chen, Kenneth W
2005-07-27 22:07 ` Chen, Kenneth W
2005-07-27 23:13 ` Andrew Morton
2005-07-27 23:13   ` Andrew Morton
2005-07-27 23:23   ` david mosberger
2005-07-27 23:23     ` david mosberger
2005-07-28  7:41     ` Ingo Molnar
2005-07-28  7:41       ` Ingo Molnar
2005-07-28  8:09 ` Keith Owens
2005-07-28  8:09   ` Keith Owens
2005-07-28  8:16   ` Ingo Molnar
2005-07-28  8:16     ` Ingo Molnar
2005-07-28  9:09     ` Ingo Molnar
2005-07-28  9:09       ` Ingo Molnar
2005-07-28  8:31   ` Nick Piggin
2005-07-28  8:31     ` Nick Piggin
2005-07-28  8:35     ` Ingo Molnar
2005-07-28  8:35       ` Ingo Molnar
2005-07-28  8:48       ` Nick Piggin
2005-07-28  8:48         ` Nick Piggin
2005-07-28  9:16         ` Ingo Molnar
2005-07-28  9:16           ` Ingo Molnar
2005-07-28  9:19           ` Ingo Molnar
2005-07-28  9:19             ` Ingo Molnar
2005-07-28  9:34           ` Nick Piggin
2005-07-28  9:34             ` Nick Piggin
2005-07-28 10:04             ` Ingo Molnar
2005-07-28 10:04               ` Ingo Molnar
2005-07-28 10:29               ` Nick Piggin
2005-07-28 10:29                 ` Nick Piggin
2005-07-28 19:14 ` Chen, Kenneth W
2005-07-28 19:14   ` Chen, Kenneth W
2005-07-29  7:04   ` Ingo Molnar
2005-07-29  7:04     ` Ingo Molnar
2005-07-29  7:07     ` Ingo Molnar
2005-07-29  7:07       ` Ingo Molnar
2005-07-29  8:30       ` Eric Dumazet
2005-07-29  8:30         ` Eric Dumazet
2005-07-29  8:44         ` Ingo Molnar
2005-07-29  8:44           ` Ingo Molnar
2005-07-31 16:27         ` hashed spinlocks Daniel Walker
2005-07-31 18:46           ` David S. Miller
2005-07-31 19:06             ` Daniel Walker
2005-07-31 19:11               ` David S. Miller
2005-07-31 19:16                 ` Daniel Walker
2005-07-29  9:17       ` Add prefetch switch stack hook in scheduler function Peter Zijlstra
2005-07-29  9:17         ` Peter Zijlstra
2005-07-29 10:52         ` Ingo Molnar
2005-07-29 10:52           ` Ingo Molnar
2005-07-29  7:22 ` Chen, Kenneth W
2005-07-29  7:22   ` Chen, Kenneth W
2005-07-29  8:28   ` Ingo Molnar
2005-07-29  8:28     ` Ingo Molnar
2005-07-29  9:02     ` Russell King
2005-07-29  9:02       ` Russell King
2005-07-29  9:45       ` Ingo Molnar [this message]
2005-07-29  9:45         ` Ingo Molnar
2005-07-29  7:38 ` Keith Owens
2005-07-29  7:38   ` Keith Owens
2005-07-29  7:45 ` Keith Owens
2005-07-29  7:45   ` Keith Owens
2005-07-29  8:02 ` Chen, Kenneth W
2005-07-29  8:02   ` Chen, Kenneth W
2005-07-29  8:08 ` Chen, Kenneth W
2005-07-29  8:08   ` Chen, Kenneth W
2005-07-29  8:30 ` Chen, Kenneth W
2005-07-29  8:30   ` Chen, Kenneth W
2005-07-29  8:35   ` Ingo Molnar
2005-07-29  8:35     ` Ingo Molnar
2005-07-29  8:39 ` Chen, Kenneth W
2005-07-29  8:39   ` Chen, Kenneth W
  -- strict thread matches above, loose matches on Subject: below --
2005-07-29 15:18 linux
2005-07-29 15:49 ` Ingo Molnar

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=20050729094519.GA12975@elte.hu \
    --to=mingo@elte.hu \
    --cc=David.Mosberger@acm.org \
    --cc=akpm@osdl.org \
    --cc=kaos@ocs.com.au \
    --cc=kenneth.w.chen@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.