From: Chris Mason <mason@suse.com>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
ReiserFS List <reiserfs-list@namesys.com>,
Manuel Krause <manuel.krause@mb.tu-ilmenau.de>,
"J.A. Magallon" <jamagallon@able.es>
Subject: Re: [PATCH] data logging patches available for 2.4.21-preX
Date: 27 Jan 2003 13:33:22 -0500 [thread overview]
Message-ID: <1043692402.15680.58.camel@tiny.suse.com> (raw)
In-Reply-To: <200301271914.26312.Dieter.Nuetzel@hamburg.de>
On Mon, 2003-01-27 at 13:14, Dieter Nützel wrote:
> Hello Chris,
>
> as always very nice work!
> I have it now running fine on top of 2.4.21-pre3-jam3 (2.4.21-pre3aa1).
> Some fiddling was necessary but went smooth after all.
> My /home partition is mounted with -o data=ordered and the performance is
> great. Sorry, no real benchmarks, yet.
>
Thanks for trying them out.
> But some question stay open:
> Where is 01-akpm-sync_fs-fix-2.diff
01-akpm-sync_fs-fix-2.diff is in the 2.4.21 data logging directory you
linked to below.
> and 01-iput-deadlock-fix.diff?
This is in the namesys pending directory, but doesn't apply cleanly
yet. I'm rediffing both the quota code and the data logging code on top
of 01-iput-deadlock-fix (or I might just steal Manuel's rediff, which is
still in my linuxworld backlog).
> Isn't it needed anylonger 'cause you merged them and SuSE's ftp isn't updated
> yet? All files are the "old" one's from 15. January.
> ftp://ftp.suse.com/pub/people/mason/patches/data-logging/2.4.21
>
> What about patch-2.4.20.rfs.06.05-transaction-overflow-fix-0.diff?
> Should I put it on top, too?
That is included in 05-data-logging-33.
-chris
next prev parent reply other threads:[~2003-01-27 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 18:14 [PATCH] data logging patches available for 2.4.21-preX Dieter Nützel
2003-01-27 18:33 ` Chris Mason [this message]
2003-01-27 18:49 ` Dieter Nützel
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=1043692402.15680.58.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=manuel.krause@mb.tu-ilmenau.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox