From: "Stephen C. Tweedie" <sct@redhat.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Andreas Dilger <adilger@enel.ucalgary.ca>,
Andreas Dilger <adilger@turbolinux.com>,
linux-kernel@vger.kernel.org, "Theodore Y. Ts'o" <tytso@mit.edu>,
Ext2 development mailing list <ext2-devel@lists.sourceforge.net>
Subject: Re: [Ext2-devel] Re: [RFC] ext2_new_block() behaviour
Date: Wed, 3 Jan 2001 12:16:09 +0000 [thread overview]
Message-ID: <20010103121609.C1290@redhat.com> (raw)
In-Reply-To: <200101030147.f031lPa21470@webber.adilger.net> <Pine.GSO.4.21.0101022216250.13824-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0101022216250.13824-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Tue, Jan 02, 2001 at 10:37:50PM -0500
Hi,
On Tue, Jan 02, 2001 at 10:37:50PM -0500, Alexander Viro wrote:
> Umm... OK, the last argument is convincing. Thanks...
>
> BTW, what was the reason behind doing preallocation for directories on
> ext2_bread() level? We both buy ourselves an oddity in directory structure
> (preallocated blocks become refered from the inode immediately and they
> are beyond i_size) and get more complicated ext2_alloc_block(). What do
> we win here?
Having preallocated blocks allocated immediately is deliberate:
directories grow slowly and remain closed most of the time, so the
normal preallocation regime of only preallocating open files and
discarding preallocation on close just doesn't work.
--Stephen
-
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-03 12:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 22:13 [CFT][RFC] ext2_new_inode() fixes and cleanup Alexander Viro
2000-11-30 23:18 ` Theodore Y. Ts'o
2000-12-01 12:55 ` Alexander Viro
2000-12-01 8:27 ` Andreas Dilger
2000-12-01 11:28 ` Alexander Viro
2001-01-02 23:33 ` [RFC] ext2_new_block() behaviour Alexander Viro
2001-01-03 1:47 ` Andreas Dilger
2001-01-03 3:37 ` Alexander Viro
2001-01-03 12:16 ` Stephen C. Tweedie [this message]
2001-01-03 16:12 ` [Ext2-devel] " Alexander Viro
2001-01-04 4:42 ` Oliver Xymoron
2001-01-04 5:06 ` Alexander Viro
2001-01-04 5:15 ` Oliver Xymoron
2001-01-04 22:04 ` Stephen C. Tweedie
2001-01-04 22:31 ` Alexander Viro
2001-01-04 20:48 ` -bird tree " Marcelo Tosatti
2001-01-04 23:25 ` Stephen C. Tweedie
2001-01-05 7:06 ` Andreas Dilger
2001-01-05 11:29 ` Stephen C. Tweedie
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=20010103121609.C1290@redhat.com \
--to=sct@redhat.com \
--cc=adilger@enel.ucalgary.ca \
--cc=adilger@turbolinux.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--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