From: Chris Mason <mason@suse.com>
To: John Dalbec <jpdalbec@ysu.edu>
Cc: reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: [PATCH] finally... data logging for 2.4.20-pre10
Date: 24 Oct 2002 09:12:50 -0400 [thread overview]
Message-ID: <1035465170.30133.95.camel@tiny> (raw)
In-Reply-To: <3DB7ECDB.5070905@ysu.edu>
On Thu, 2002-10-24 at 08:51, John Dalbec wrote:
> Manuel Krause wrote:
> > On 10/23/2002 09:01 PM, John Dalbec wrote:
> >
> >> Chris Mason wrote:
> >>
> >>> Hello all,
> >>>
> >>> I've uploaded new data logging code against 2.4.20-pre10 to
> >>> ftp.suse.com/pub/people/mason/patches/data-logging/2.4.20
>
> Does anyone know what kernel was used for the patches in
> ftp.suse.com/pub/people/mason/patches/data-logging ? Are they against
> 2.4.19? The README doesn't say.
They are against 2.4.19, but it is a slightly older set of patches.
They are good for benchmarking, but I would suggest using the 2.4.20-pre
patches for serious testing.
I'll try and upload the latest stuff against 2.4.19 today, this is what
the current suse kernel is based on, so it is by far the best tested of
the data logging series.
-chris
next prev parent reply other threads:[~2002-10-24 13:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 19:24 [PATCH] finally... data logging for 2.4.20-pre10 Chris Mason
2002-10-15 22:16 ` Manuel Krause
2002-10-18 13:41 ` Manuel Krause
2002-10-23 19:01 ` John Dalbec
2002-10-23 21:59 ` Manuel Krause
2002-10-24 12:51 ` John Dalbec
2002-10-24 13:12 ` Chris Mason [this message]
2002-11-12 15:39 ` Toby Dickenson
2002-11-18 14:31 ` John Dalbec
-- strict thread matches above, loose matches on Subject: below --
2002-10-15 22:29 JP Howard
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=1035465170.30133.95.camel@tiny \
--to=mason@suse.com \
--cc=jpdalbec@ysu.edu \
--cc=reiserfs-list@namesys.com \
/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.