From: Andi Kleen <andi@firstfloor.org>
To: Sebastien Buisson <sebastien.buisson@bull.net>
Cc: Andi Kleen <andi@firstfloor.org>,
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: Mon, 7 Jul 2014 18:30:03 +0200 [thread overview]
Message-ID: <20140707163003.GA18735@two.firstfloor.org> (raw)
In-Reply-To: <53BA772C.6040506@bull.net>
> diff --git a/fs/Kconfig b/fs/Kconfig
> index c229f82..c08844c 100644
> --- a/fs/Kconfig
> +++ b/fs/Kconfig
> @@ -268,4 +268,13 @@ endif # NETWORK_FILESYSTEMS
> source "fs/nls/Kconfig"
> source "fs/dlm/Kconfig"
>
> +config BH_LRU_SIZE
> + int
> + range 8 64
> + default "16"
So who sets it then?
You need it for ext4 and quota right? So this combination
should set it at least. Something like (unested)
It would be also good to audit or test other file systems if they need the
same if that's possible.
config BH_LARGE_LRU
bool
depends on (EXT4_FS && QUOTA)
config BH_LRU_SIZE
....
default "16" if BH_LARGE_LRU
default "8" if !BH_LARGE_LRU
-Andi
next prev parent reply other threads:[~2014-07-07 16:30 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
2014-07-07 10:32 ` Sebastien Buisson
2014-07-07 16:30 ` Andi Kleen [this message]
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=20140707163003.GA18735@two.firstfloor.org \
--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.