From: Andrew Morton <akpm@osdl.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: prezeroing V6 [2/3]: ScrubD
Date: Tue, 08 Feb 2005 01:09:47 +0000 [thread overview]
Message-ID: <20050207170947.239f8696.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0502071646170.29971@schroedinger.engr.sgi.com>
Christoph Lameter <clameter@sgi.com> wrote:
>
> > What were the benchmarking results for this work? I think you had some,
> > but this is pretty vital info, so it should be retained in the changelogs.
>
> Look at the early posts. I plan to put that up on the web. I have some
> stats attached to the end of this message from an earlier post.
But that's a patch-specific microbenchmark, isn't it? Has this work been
benchmarked against real-world stuff?
> > Should we be managing the kernel threads with the kthread() API?
>
> What would you like to manage?
Startup, perhaps binding the threads to their cpus too.
next prev parent reply other threads:[~2005-02-08 1:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0501211228430.26068@schroedinger.engr.sgi.com>
[not found] ` <1106828124.19262.45.camel@hades.cambridge.redhat.com>
[not found] ` <20050202153256.GA19615@logos.cnet>
2005-02-07 19:30 ` prezeroing V6 [0/3]: Changes and overview Christoph Lameter
2005-02-07 19:31 ` prezeroing V6 [1/3]: clear_pages Christoph Lameter
2005-02-07 19:31 ` prezeroing V6 [2/3]: ScrubD Christoph Lameter
2005-02-08 0:30 ` Andrew Morton
2005-02-08 0:49 ` Christoph Lameter
2005-02-08 1:09 ` Andrew Morton [this message]
2005-02-08 1:15 ` Christoph Lameter
2005-02-08 1:35 ` Andrew Morton
2005-02-08 16:11 ` Christoph Lameter
2005-02-08 20:27 ` Andrew Morton
2005-02-08 20:51 ` Christoph Lameter
2005-02-08 23:32 ` cliff white
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=20050207170947.239f8696.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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