From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Andrew Morton <akpm@zip.com.au>,
lkml <linux-kernel@vger.kernel.org>, Steve Lord <lord@sgi.com>
Subject: Re: [patch] delayed disk block allocation
Date: Sun, 03 Mar 2002 22:10:25 -0500 [thread overview]
Message-ID: <3C82E5A1.714081EA@mandrakesoft.com> (raw)
In-Reply-To: <3C7F3B4A.41DB7754@zip.com.au> <E16hhuI-0000S6-00@starship.berlin>
Daniel Phillips wrote:
> On March 1, 2002 09:26 am, Andrew Morton wrote:
> > A bunch of patches which implement allocate-on-flush for 2.5.6-pre1 are
> > available at http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.6-pre1/dalloc-10-core.patch
> > - Core functions
> > and
> http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.6-pre1/dalloc-20-ext2.patch
> > - delalloc implementation for ext2.
> Wow, this is massive. Why did you write [patch] instead of [PATCH]? ;-) I'm
> surprised there aren't any comments on this patch so far, that should teach
> you to post on a Friday afternoon.
My only comment is: how fast can we get delalloc into 2.5.x for further
testing and development?
IMNSHO there are few comments because I believe that few people actually
realize the benefits of delalloc. My ext2 filesystem with --10--
percent fragmentation could sure use code like this, though.
> > But it may come unstuck when applied to swapcache.
>
> You're not even trying to apply this to swap cache right now are you?
This is a disagreement akpm and I have, actually :)
I actually would rather that it was made a requirement that all
swapfiles are "dense", so that new block allocation NEVER must be
performed when swapping.
> There is also my nefarious plan to make
> struct pages refer to variable-binary-sized objects, including smaller than
> 4K PAGE_SIZE.
sigh...
--
Jeff Garzik |
Building 1024 |
MandrakeSoft | Choose life.
next prev parent reply other threads:[~2002-03-04 3:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 8:26 [patch] delayed disk block allocation Andrew Morton
2002-03-04 2:08 ` Daniel Phillips
2002-03-04 3:10 ` Jeff Garzik [this message]
2002-03-04 7:27 ` Andrew Morton
2002-03-04 5:04 ` Mike Fedyk
2002-03-04 5:31 ` Andreas Dilger
2002-03-04 5:40 ` Mike Fedyk
2002-03-04 6:14 ` Andreas Dilger
2002-03-04 5:41 ` Jeff Garzik
2002-03-04 6:18 ` Andreas Dilger
2002-03-04 15:02 ` Hans Reiser
2002-03-06 12:59 ` Pavel Machek
2002-03-04 7:53 ` Andrew Morton
2002-03-04 8:06 ` Daniel Phillips
2002-03-04 8:34 ` Andrew Morton
2002-03-04 7:20 ` Andrew Morton
2002-03-04 9:23 ` Daniel Phillips
-- strict thread matches above, loose matches on Subject: below --
2002-03-04 14:54 rwhron
2002-03-04 15:10 ` Jeff Garzik
2002-03-07 12:06 Etienne Lorrain
2002-03-07 14:47 ` Steve Lord
2002-03-07 17:30 ` Mike Fedyk
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=3C82E5A1.714081EA@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=lord@sgi.com \
--cc=phillips@bonn-fries.net \
/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.