From: Coywolf Qi Hunt <coywolf@gmail.com>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-ia64@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Prefetch kernel stacks to speed up context switch
Date: Wed, 7 Sep 2005 16:52:17 +0800 [thread overview]
Message-ID: <2cd57c900509070152518fac06@mail.gmail.com> (raw)
In-Reply-To: <200509070829.j878TSg25898@unix-os.sc.intel.com>
On 9/7/05, Chen, Kenneth W <kenneth.w.chen@intel.com> wrote:
> Repost previously discussed patch (on Jul 27, 2005). Ingo did
> the same thing for all arch with 471 lines of patch. I'm still
> advocating this little 30 lines patch, of 6 lines introduces
> prefetch_stack() generic interface.
>
> Andrew, please consider -mm inclusion. Or advise me what I need
> to do to take this forward. Thanks.
>
> - Ken
Do you have any benchmarks?
--
Coywolf Qi Hunt
http://sosdg.org/~coywolf/
next prev parent reply other threads:[~2005-09-07 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 8:28 Prefetch kernel stacks to speed up context switch Chen, Kenneth W
2005-09-07 8:52 ` Coywolf Qi Hunt [this message]
2005-09-07 16:14 ` Grant Grundler
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=2cd57c900509070152518fac06@mail.gmail.com \
--to=coywolf@gmail.com \
--cc=akpm@osdl.org \
--cc=kenneth.w.chen@intel.com \
--cc=linux-ia64@vger.kernel.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