From: Andrew Morton <akpm@zip.com.au>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [prepatch] address_space-based writeback
Date: Mon, 15 Apr 2002 01:47:39 -0700 [thread overview]
Message-ID: <3CBA93AB.A20F0FF7@zip.com.au> (raw)
In-Reply-To: <3CB4203D.C3BE7298@zip.com.au>
An update to these patches is at
http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.8/
All work at this time is on
dallocbase-10-page_alloc_fail.patch
dallocbase-35-pageprivate_fixes.patch
dallocbase-55-ext2_dir.patch
dallocbase-60-page_accounting.patch
ratcache-pf_memalloc.patch
mempool-node.patch
dallocbase-70-writeback.patch
ttd (my current 2.5 things-to-do-list, just for fun)
none of the patches beyond these have even been tested in a week..
The new buffer<->page relationship rules seem to be working
out OK. In a six-hour stress test on a quad Xeon with
1k blocksize ext3 in ordered-data mode there was one failure:
a block in a file which came up with wrong data. There appears
to be a race in ext3 or the patch or 2.5 or something somewhere.
Still hunting this one.
It is all relatively stable now. ramdisk, loop, reiserfs, ext2,
ext3-ordered, ext3-journalled, JFS and vfat have been tested.
minixfs and sysvfs are broken with these patches. They rely
on preservation of directory data outside i_size. Will fix.
-
prev parent reply other threads:[~2002-04-15 8:48 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 11:21 [prepatch] address_space-based writeback Andrew Morton
2002-04-10 11:34 ` Alexander Viro
2002-04-10 19:16 ` Andrew Morton
2002-04-10 20:53 ` Alexander Viro
2002-04-10 22:12 ` Jan Harkes
2002-04-10 21:44 ` Andrew Morton
2002-04-10 22:56 ` Anton Altaparmakov
2002-04-10 22:31 ` Andrew Morton
2002-04-11 20:20 ` Linus Torvalds
2002-04-11 20:41 ` Alexander Viro
2002-04-11 21:27 ` Andrew Morton
2002-04-11 22:55 ` Andreas Dilger
2002-04-11 22:49 ` Andrew Morton
2002-04-12 0:12 ` Linus Torvalds
2002-04-11 23:10 ` Christoph Hellwig
2002-04-11 23:22 ` Anton Altaparmakov
2002-04-11 23:03 ` Andrew Morton
2002-04-12 4:19 ` Bill Davidsen
2002-04-12 1:15 ` Anton Altaparmakov
2002-04-12 1:37 ` Linus Torvalds
2002-04-12 7:57 ` Anton Altaparmakov
2002-04-27 15:53 ` Jan Harkes
2002-04-28 3:03 ` Anton Altaparmakov
2002-04-29 9:03 ` Nikita Danilov
2002-04-29 11:11 ` Anton Altaparmakov
2002-04-29 11:59 ` Nikita Danilov
2002-04-29 12:34 ` Anton Altaparmakov
2002-04-29 13:01 ` Christoph Hellwig
2002-04-30 17:19 ` Denis Vlasenko
2002-04-30 13:15 ` john slee
2002-04-30 13:24 ` Billy O'Connor
2002-04-30 13:36 ` jlnance
2002-04-30 13:40 ` Keith Owens
2002-05-01 19:18 ` Denis Vlasenko
2002-05-02 8:49 ` Anton Altaparmakov
2002-05-03 15:35 ` Denis Vlasenko
2002-05-03 12:49 ` Helge Hafting
2002-05-03 22:47 ` Denis Vlasenko
2002-05-03 21:50 ` Anton Altaparmakov
2002-05-05 0:46 ` Denis Vlasenko
2002-05-03 7:56 ` Pavel Machek
2002-05-03 14:48 ` Rob Landley
2002-05-05 0:42 ` Denis Vlasenko
2002-04-30 16:12 ` Peter Wächtler
2002-04-10 23:02 ` Jan Harkes
2002-04-10 19:29 ` Jeremy Jackson
2002-04-10 19:41 ` Andrew Morton
2002-04-15 8:47 ` Andrew Morton [this message]
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=3CBA93AB.A20F0FF7@zip.com.au \
--to=akpm@zip.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox