From: Michael Rubin <mrubin@google.com>
To: Curt Wohlgemuth <curtw@google.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: PATCH: Making mb_history length a dynamic tunable
Date: Sat, 18 Apr 2009 00:51:43 -0700 [thread overview]
Message-ID: <532480950904180051m3226b309wc42cded4e73be028@mail.gmail.com> (raw)
In-Reply-To: <6601abe90904071020gdce65d2madc6df30c182c5cd@mail.gmail.com>
On Tue, Apr 7, 2009 at 10:20 AM, Curt Wohlgemuth <curtw@google.com> wrote:
> Hi:
>
> Since we frequently run in memory-constrained systems with many partitions,
> the ~68K for each partition for the mb_history buffer can be excessive. The
> following creates a new proc file under /proc/fs/ext4/ to control the number
> of entries at mount time.
>
> If the notion of a history length tunable is okay, but the location should
> be under /sys/fs/ext4/ instead of /proc/fs/ext4/, I can change this. The
> leftover files under /proc/fs/ext4/<partition>/ are a bit confusing to me.
>
Does the silence mean that there is no interest in this CL?
We thought making this a run time tunable would be cool.
mrubin
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-04-18 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 17:20 PATCH: Making mb_history length a dynamic tunable Curt Wohlgemuth
2009-04-18 7:51 ` Michael Rubin [this message]
2009-04-18 12:53 ` Theodore Tso
2009-04-20 3:22 ` Andreas Dilger
2009-04-20 18:53 ` Curt Wohlgemuth
2009-04-20 19:26 ` Theodore Tso
2009-05-02 0:31 ` [PATCH] ext4: Make the length of the mb_history file tunable Theodore Ts'o
2009-05-02 16:30 ` Curt Wohlgemuth
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=532480950904180051m3226b309wc42cded4e73be028@mail.gmail.com \
--to=mrubin@google.com \
--cc=curtw@google.com \
--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).