From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] GFS2: Improve statfs and quota usability
Date: Tue, 13 Oct 2009 16:38:23 +0100 [thread overview]
Message-ID: <1255448303.6052.567.camel@localhost.localdomain> (raw)
In-Reply-To: <20091013144902.GE3555@ether.msp.redhat.com>
Hi,
On Tue, 2009-10-13 at 09:49 -0500, Benjamin Marzinski wrote:
> GFS2 now has three new mount options, statfs_quantum, quota_quantum and
> statfs_percent. statfs_quantum and quota_quantum simply allow you to set the
> tunables of the same name. Setting setting statfs_quantum to 0 will
> also turn on the statfs_slow tunable. statfs_percent is both a mount option
> and a tunable. It accepts an integer between 0 and 100. Numbers between 1 and
> 100 will cause GFS2 to do any early sync when the local number of blocks free
> changes by at least statfs_percent from the totoal number of blocks free.
> Setting statfs_percent to 0 disables this.
>
> Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
> ---
> fs/gfs2/incore.h | 5 ++++
> fs/gfs2/ops_fstype.c | 15 ++++++++++---
> fs/gfs2/quota.c | 21 ++++++++++++++++---
> fs/gfs2/quota.h | 2 +
> fs/gfs2/super.c | 56 +++++++++++++++++++++++++++++++++++++++++++++++++++
> fs/gfs2/sys.c | 33 +++++++++++++++++-------------
> 6 files changed, 112 insertions(+), 20 deletions(-)
>
Can you drop out the bit adding the new sysfs file? The plan is to
reduce those in favour of using mount options as much as possible. Other
than that, it looks good to me.
When we update the docs we should add something to ensure that people
realise that setting the options via the mount command line is the
preferred method,
Steve.
next prev parent reply other threads:[~2009-10-13 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 14:49 [Cluster-devel] [PATCH] GFS2: Improve statfs and quota usability Benjamin Marzinski
2009-10-13 15:38 ` Steven Whitehouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-20 15:34 Benjamin Marzinski
2010-01-20 16:45 ` Benjamin Marzinski
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=1255448303.6052.567.camel@localhost.localdomain \
--to=swhiteho@redhat.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;
as well as URLs for NNTP newsgroup(s).