From: Benjamin LaHaise <bcrl@kvack.org>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Jan Kara <jack@suse.cz>, Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: add noorlov parameter to avoid spreading of directory inodes
Date: Wed, 2 Oct 2013 11:31:01 -0400 [thread overview]
Message-ID: <20131002153101.GE4353@kvack.org> (raw)
In-Reply-To: <524C3574.7020106@redhat.com>
On Wed, Oct 02, 2013 at 10:02:12AM -0500, Eric Sandeen wrote:
> I'm right with you on thinking a mount option should be a last resort.
>
> One thing I'm curious about - what changed from ext3 to ext4? I thought
> both defaulted to orlov and the same type of allocation behavior, more
> or less. I guess one change is that the "oldalloc" mount
> option went away.
> (if it does come back, it should probably mirror what we had before,
> which was "oldalloc" not "noorlov" right?)
The behaviour I'm looking for is not exactly the same as the orlov
allocator or the old allocator, but something that packs files as
closely together as possible. Half of this can be achieved with
fallocate(), but reducing the spreading of directory inodes can only be
accomplished with changes to the filesystem itself. The only reason
we're using multiple subdirectories is because of contention issues with
i_mutex (our application has to either fsync() the directory or mount
with dirsync to maintain consistency) during file creation and unlink().
-ben
--
"Thought is the essence of where you are now."
next prev parent reply other threads:[~2013-10-02 15:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 16:08 [PATCH] ext4: add noorlov parameter to avoid spreading of directory inodes Benjamin LaHaise
2013-10-02 14:47 ` Jan Kara
2013-10-02 15:02 ` Eric Sandeen
2013-10-02 15:25 ` Lukáš Czerner
2013-10-02 15:31 ` Benjamin LaHaise [this message]
2013-10-02 15:57 ` Jan Kara
2013-10-02 16:44 ` Lukáš Czerner
2013-10-02 16:52 ` Benjamin LaHaise
2013-10-02 17:09 ` Lukáš Czerner
2013-10-02 16:23 ` Theodore Ts'o
2013-10-02 17:02 ` Benjamin LaHaise
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=20131002153101.GE4353@kvack.org \
--to=bcrl@kvack.org \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.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;
as well as URLs for NNTP newsgroup(s).