All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.59-dcl2
Date: Tue, 28 Jan 2003 16:17:53 -0800	[thread overview]
Message-ID: <3E371DB1.F365D2CB@digeo.com> (raw)
In-Reply-To: 1043798822.10150.318.camel@dell_ss3.pdx.osdl.net

Stephen Hemminger wrote:
> 
> Missed one item in the credits.
> 
> Also, added the Nick Piggin's anticipaatory i/o scheduler (via -mm5)
> to 2.5.59-dcl2 to evaluate the performance impact under different loads.
> 

It caused regression in David Mansfield's database test.  That was
recovered in -mm6.

  reply	other threads:[~2003-01-29  0:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28 22:51 2.5.59-dcl2 Stephen Hemminger
2003-01-28 23:10 ` 2.5.59-dcl2 Christoph Hellwig
2003-01-28 23:24   ` 2.5.59-dcl2 Stephen Hemminger
2003-01-29  0:13   ` 2.5.59-dcl2 Alan Cox
2003-01-29  0:07 ` 2.5.59-dcl2 Stephen Hemminger
2003-01-29  0:17   ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-28 23:17 2.5.59-dcl2 Matt_Domsch
2003-01-29  5:35 2.5.59-dcl2 Matt_Domsch
2003-01-29  6:51 ` 2.5.59-dcl2 Mike Anderson
2003-01-29 18:05   ` 2.5.59-dcl2 Luben Tuikov
2003-01-29 17:02 ` 2.5.59-dcl2 Mark Haverkamp
     [not found] <1043794298.10153.241.camel@dell_ss3.pdx.osdl.net.suse.lists.linux.kernel>
     [not found] ` <1043798822.10150.318.camel@dell_ss3.pdx.osdl.net.suse.lists.linux.kernel>
2003-01-29 12:35   ` 2.5.59-dcl2 Andi Kleen
2003-01-29 12:55     ` 2.5.59-dcl2 Mikael Pettersson
2003-01-29 16:53     ` 2.5.59-dcl2 Stephen Hemminger
2003-01-29 19:41 2.5.59-dcl2 Mukker, Atul
2003-01-29 20:09 ` 2.5.59-dcl2 Mark Haverkamp

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=3E371DB1.F365D2CB@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shemminger@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 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.