From: Andi Kleen <andi@firstfloor.org>
To: Sebastien Buisson <sebastien.buisson@bull.net>
Cc: <viro@zeniv.linux.org.uk>, <linux-fsdevel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Allow increasing the buffer-head per-CPU LRU size
Date: Sun, 06 Jul 2014 09:18:12 -0700 [thread overview]
Message-ID: <87y4w6sbp7.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <53B667F9.90306@bull.net> (Sebastien Buisson's message of "Fri, 4 Jul 2014 10:38:17 +0200")
Sebastien Buisson <sebastien.buisson@bull.net> writes:
> Allow increasing the buffer-head per-CPU LRU size to allow efficient
> filesystem operations that access many blocks for each transaction.
> For example, creating a file in a large ext4 directory with quota
> enabled will accesses multiple buffer heads and will overflow the LRU
> at the default 8-block LRU size:
I don't think that should be a user visible config. Most users wouldn't
know how to set it. And Linux already has far too many obscure
config options.
Either make it set implicitely by the file system config.
Or just increase it unconditionally?
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2014-07-06 16:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 8:38 [PATCH] Allow increasing the buffer-head per-CPU LRU size Sebastien Buisson
2014-07-05 7:44 ` Andreas Mohr
2014-07-06 16:18 ` Andi Kleen [this message]
2014-07-07 10:32 ` Sebastien Buisson
2014-07-07 16:30 ` Andi Kleen
2014-07-07 16:30 ` Andi Kleen
2014-07-07 22:29 ` Andrew Morton
2014-07-07 22:46 ` Andi Kleen
2014-07-08 6:28 ` Sebastien Buisson
2014-07-10 6:51 ` Sebastien Buisson
2014-07-10 7:07 ` Andrew Morton
2014-07-10 7:29 ` Sebastien Buisson
2014-07-10 7:29 ` Sebastien Buisson
2014-07-10 14:17 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2014-06-27 12:25 Sebastien Buisson
2014-06-24 15:52 Sebastien Buisson
2014-06-25 22:16 ` Andrew Morton
2014-06-26 11:44 ` Sebastien Buisson
2014-06-26 21:37 ` Andrew Morton
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=87y4w6sbp7.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastien.buisson@bull.net \
--cc=viro@zeniv.linux.org.uk \
/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.