From: Eric Sandeen <sandeen@redhat.com>
To: Zeev Tarantov <zeev.tarantov@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: problem(?) in ext4 or mke2fs
Date: Sun, 03 Apr 2011 12:21:26 -0700 [thread overview]
Message-ID: <4D98C8B6.7050806@redhat.com> (raw)
In-Reply-To: <BANLkTimRJ95zd64CPckPu9RpRwHioJdVCA@mail.gmail.com>
On 4/3/11 12:01 PM, Zeev Tarantov wrote:
> On Sun, Apr 3, 2011 at 21:56, Eric Sandeen <sandeen@redhat.com> wrote:
>> On 4/3/11 11:52 AM, Zeev Tarantov wrote:
>>> If the filesystem created with the default options is slow or has
>>> higher cpu usage, it should be changed.
>>
>> I agree. For actual striped storage, this makes it faster, but this
>> case is a problem; block-sized stripe width is never going to be good.
>> What device is this, exactly?
>
> Look in linux-2.6/drivers/staging/zram/zram.txt
OK, so it does:
/*
* To ensure that we always get PAGE_SIZE aligned
* and n*PAGE_SIZED sized I/O requests.
*/
blk_queue_physical_block_size(zram->disk->queue, PAGE_SIZE);
blk_queue_logical_block_size(zram->disk->queue,
ZRAM_LOGICAL_BLOCK_SIZE);
blk_queue_io_min(zram->disk->queue, PAGE_SIZE);
blk_queue_io_opt(zram->disk->queue, PAGE_SIZE);
These are all documented in Documentation/ABI/testing/sysfs-block.
I don't think that setting all those values in zram is necessary and/or
sufficient to achieve what is desired in the comment. io_min/io_opt
generally are set only for striped devices.
Still, mke2fsprogs should probably sanity-check for this; I'll make
sure this seems right, and send a patch.
Thanks,
-Eric
>> -Eric (losing my free airport wifi in about 8 minutes, so I may have
>> to continue this later...!)
>>
>>>> -Eric
>>>
>>> -Z.T.
>>
next prev parent reply other threads:[~2011-04-03 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 18:07 problem(?) in ext4 or mke2fs Zeev Tarantov
2011-04-03 18:40 ` Eric Sandeen
2011-04-03 18:52 ` Zeev Tarantov
2011-04-03 18:56 ` Eric Sandeen
2011-04-03 19:01 ` Zeev Tarantov
2011-04-03 19:21 ` Eric Sandeen [this message]
2011-04-04 0:40 ` Andreas Dilger
2011-04-04 0:50 ` Andreas Dilger
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=4D98C8B6.7050806@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=zeev.tarantov@gmail.com \
/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