mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Mon, 7 Feb 2005 17:09:47 -0800	[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.

  reply	other threads:[~2005-02-08  1:04 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-21 20:29 A scrub daemon (prezeroing) Christoph Lameter
2005-01-27 12:15 ` David Woodhouse
2005-01-27 13:12   ` Robin Holt
2005-01-27 13:14     ` David Woodhouse
2005-01-27 17:02       ` Christoph Lameter
2005-02-08 11:31     ` Ralf Baechle
2005-02-02 15:32   ` Marcelo Tosatti
2005-02-02 19:05     ` Christoph Lameter
2005-02-02 16:31       ` Marcelo Tosatti
2005-02-02 21:31         ` Christoph Lameter
2005-02-02 21:39         ` David Woodhouse
2005-02-03  3:06         ` Rik van Riel
2005-02-03 23:39           ` Paul Mackerras
2005-02-04  0:59             ` Christoph Lameter
2005-02-04  5:30               ` Paul Mackerras
2005-02-04  6:26                 ` Christoph Lameter
2005-02-04  6:43                   ` Nick Piggin
2005-02-04  6:50                     ` Christoph Lameter
2005-02-04  9:20                   ` Paul Mackerras
2005-02-04  9:28                     ` Andi Kleen
2005-02-04 17:02                     ` Christoph Lameter
2005-02-04 22:25                       ` Paul Mackerras
2005-02-02 21:00     ` Maciej W. Rozycki
2005-02-02 21:33       ` David Woodhouse
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
2005-02-07 19:32       ` prezeroing V6 [3/3]: Altix SN2 Block Transfer Engine Zeroing Driver Christoph Lameter

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

all inboxes | Powered by JetHome®