From: Daniel Phillips <phillips@innominate.de>
To: Alexander Viro <viro@math.psu.edu>,
linux-kernel@vger.kernel.org,
Rik van Riel <riel@conectiva.com.br>
Subject: Re: [RFC] Generic deferred file writing
Date: Mon, 01 Jan 2001 21:00:36 +0100 [thread overview]
Message-ID: <3A50E1E4.26A8124A@innominate.de> (raw)
In-Reply-To: <Pine.GSO.4.10.10101010332330.1050-100000@zeus.fh-brandenburg.de> <Pine.GSO.4.21.0012312220290.7648-100000@weyl.math.psu.edu>
Alexander Viro wrote:
> GFP_BUFFER _may_ become an issue if we move bitmaps into pagecache.
> Then we'll need a per-address_space gfp_mask. Again, patches exist
> and had been tested (not right now - I didn't port them to current
> tree yet). Bugger if I remember whether they were posted or not - they've
> definitely had been mentioned on linux-mm, but IIRC I had sent the
> modifications of VM code only to Jens. I can repost them.
Please, and I'll ask Rik to post them on the kernelnewbies.org patch
page. (Rik?) Putting bitmaps and group descriptors into the page cache
will allow the current adhoc bitmap and groupdesc caching code to be
deleted - the for-real cache should have better lru, be more efficient
to access, not need special locking and won't have an arbitrary limit on
number of cached bitmaps. About 300 lines of spagetti gone. I suppose
the group descriptor pages still need to be locked in memory so we can
address them through a table instead of searching the hash. OK, this
must be what you meant by a 'proper' fix to the ialloc group desc bug I
posted last month, which by the way is *still* there. How about
applying my patch in the interim? It's a real bug, it just doesn't
trigger often.
> Some pieces of balloc.c cleanup had been posted on fsdevel. Check the
> archives. They prepare the ground for killing lock_super() contention
> on ext2_new_inode(), but that part wasn't there back then.
>
> I will start -bird (aka FS-CURRENT) branch as soon as Linus opens 2.4.
> Hopefully by the time of 2.5 it will be tested well enough. Right now
> it exists as a large patchset against more or less recent -test<n> and
> I'm waiting for slowdown of the changes in main tree to put them all
> together.
It would be awfully nice to have those patches available via ftp.
Web-based mail archives don't make it because you can't generally can't
get the patches out intact - the tabs get expanded and other noise
inserted.
--
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-01 20:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10012311726230.1671-100000@penguin.transmeta.com>
2001-01-01 2:50 ` [RFC] Generic deferred file writing Roman Zippel
2001-01-01 3:47 ` Alexander Viro
2001-01-01 12:44 ` Roman Zippel
2001-01-01 15:16 ` Alexander Viro
2001-01-02 3:00 ` Roman Zippel
2001-01-02 5:00 ` Alexander Viro
2001-01-02 16:53 ` Roman Zippel
2001-01-01 20:00 ` Daniel Phillips [this message]
2000-12-30 3:16 test13-pre6 Linus Torvalds
2000-12-30 18:58 ` [RFC] Generic deferred file writing Daniel Phillips
2000-12-30 20:05 ` Linus Torvalds
2000-12-30 20:06 ` Alexander Viro
2000-12-30 20:21 ` Linus Torvalds
2000-12-30 21:10 ` Andreas Dilger
2000-12-30 21:46 ` Alexander Viro
2000-12-30 23:12 ` Daniel Phillips
2000-12-30 22:00 ` Eric W. Biederman
2000-12-30 22:44 ` Linus Torvalds
2000-12-31 0:26 ` Eric W. Biederman
2000-12-31 1:02 ` Andrea Arcangeli
2000-12-31 1:13 ` Chris Wedgwood
2000-12-31 1:50 ` Alexander Viro
2000-12-31 2:34 ` Andrea Arcangeli
2000-12-31 2:09 ` Roman Zippel
2000-12-31 2:28 ` Linus Torvalds
2000-12-31 12:58 ` Roman Zippel
2000-12-31 14:38 ` Andrea Arcangeli
2000-12-31 16:33 ` Linus Torvalds
2000-12-31 16:50 ` Andrea Arcangeli
2000-12-31 16:51 ` Alexander Viro
2000-12-31 17:12 ` Linus Torvalds
2000-12-31 18:30 ` Daniel Phillips
2000-12-31 18:44 ` Linus Torvalds
2000-12-31 19:10 ` Daniel Phillips
2000-12-31 19:31 ` Linus Torvalds
2000-12-31 21:03 ` Roman Zippel
2000-12-31 21:32 ` Linus Torvalds
2001-01-02 18:27 ` Chris Mason
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=3A50E1E4.26A8124A@innominate.de \
--to=phillips@innominate.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=viro@math.psu.edu \
/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