From: Erik Andersen <andersen@codepoet.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18pre3-ac1-aia21 (IDE patches)
Date: Sun, 13 Jan 2002 18:50:12 -0700 [thread overview]
Message-ID: <20020114015012.GA17253@codepoet.org> (raw)
In-Reply-To: <5.1.0.14.2.20020113232757.04f34ec0@pop.cus.cam.ac.uk> <E16PwJO-0000F8-00@the-village.bc.nu>
In-Reply-To: <E16PwJO-0000F8-00@the-village.bc.nu>
On Mon Jan 14, 2002 at 01:53:22AM +0000, Alan Cox wrote:
> > Alan's -ac series is back! To celebrate this I added in the IDE patches and
> > an NTFS update which dramatically reduces the number of vmalloc()s and have
> > posted the resulting (tested) patch (to be applied on top of
> > 2.4.18pre3-ac1) at below URL.
>
> Andre's IDE patch is in the ac2 cut. I took it out just to make testing easier
> in case other people found -ac1 wasnt as reliable as I did 8)
Will -ac2 be hitting the mirrors shortly then? BTW, you
mentioned in your earlier email you excluded the low-latency
patches. Mind if I ask which of the many you are using?
mini-ll? full-ll? The sched-O1-H6 patch?
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2002-01-14 1:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-14 1:07 Linux 2.4.18pre3-ac1-aia21 (IDE patches) Anton Altaparmakov
2002-01-14 1:44 ` IDE Patches bring amazing performance gain!!! Anton Altaparmakov
2002-01-14 4:40 ` Andre Hedrick
2002-01-14 15:10 ` J.A. Magallon
2002-01-14 14:24 ` Matthias Andree
2002-01-14 1:53 ` Linux 2.4.18pre3-ac1-aia21 (IDE patches) Anton Altaparmakov
2002-01-14 9:35 ` Alan Cox
2002-01-14 9:46 ` Anton Altaparmakov
2002-01-14 1:53 ` Alan Cox
2002-01-14 1:50 ` Erik Andersen [this message]
2002-01-14 9:35 ` Alan Cox
2002-01-14 2:10 ` Andrew Morton
2002-01-14 2:27 ` Anton Altaparmakov
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=20020114015012.GA17253@codepoet.org \
--to=andersen@codepoet.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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.