From: "Alexander V. Lukyanov" <lav@netis.ru>
To: linux-ext4@vger.kernel.org
Subject: Re: PATCH: allow inode_readahead_blks=0
Date: Wed, 17 Nov 2010 10:48:54 +0300 [thread overview]
Message-ID: <20101117074850.GA29191@proxy> (raw)
In-Reply-To: <20101116080546.GA7949@proxy>
On Tue, Nov 16, 2010 at 11:05:46AM +0300, Alexander V. Lukyanov wrote:
> Currently the value 0 is disallowed, as it is not a power of 2.
BTW, the default value inode_readahead_blks=32 gives me troubles: it raises
load average and increases request latency on a busy squid server. I
explain it by random access to large number of files which are present in
the squid cache.
BTW2: the value of 0 should be allowed, it is explicitly used by the code:
/*
* If we need to do any I/O, try to pre-readahead extra
* blocks from the inode table.
*/
if (EXT4_SB(sb)->s_inode_readahead_blks) {
...
}
--
Alexander.
prev parent reply other threads:[~2010-11-17 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 8:05 PATCH: allow inode_readahead_blks=0 Alexander V. Lukyanov
2010-11-17 7:48 ` Alexander V. Lukyanov [this message]
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=20101117074850.GA29191@proxy \
--to=lav@netis.ru \
--cc=linux-ext4@vger.kernel.org \
/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).