From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@sun.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 3/3] ext4: Use readahead when reading an inode from the inode table
Date: Fri, 26 Sep 2008 08:47:24 -0500 [thread overview]
Message-ID: <48DCE7EC.5000801@redhat.com> (raw)
In-Reply-To: <20080926082107.GT10950@webber.adilger.int>
Andreas Dilger wrote:
> On Sep 24, 2008 12:53 -0400, Theodore Ts'o wrote:
>> @@ -514,8 +514,10 @@ static void ext4_put_super(struct super_block *sb)
>> + if (sbi->s_proc) {
>> + remove_proc_entry("inode_readahead_bits", sbi->s_proc);
>> remove_proc_entry(sb->s_id, ext4_proc_root);
>
> As a general UI interface, specifying the "bits to shift the filesystem
> block number" seems like an easy-to-implement but is fairly bad from
> a usability point of view. I'd much prefer to specify this as a
> number of kB to readahead, and it can be converted internally to the
> number of blocks to readahead. It isn't fatal if we do a bit of rounding
> on the input value to match a full blocksize.
Or specify that it must be a power of two in some range, and reject
other values - either way.
I had the same thought about the nr of bits as a user input value...
-Eric
next prev parent reply other threads:[~2008-09-26 13:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 16:53 [PATCH 1/3] ext4: move /proc setup and teardown out of mballoc.c Theodore Ts'o
2008-09-24 16:53 ` [PATCH 2/3] ext4: Combine proc file handling into a single set of functions Theodore Ts'o
2008-09-24 16:53 ` [PATCH 3/3] ext4: Use readahead when reading an inode from the inode table Theodore Ts'o
2008-09-26 8:21 ` Andreas Dilger
2008-09-26 13:47 ` Eric Sandeen [this message]
2008-09-28 4:27 ` Theodore Tso
2008-10-02 2:17 ` Andreas Dilger
2008-10-03 3:56 ` Theodore Tso
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=48DCE7EC.5000801@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--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 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.