From: Jan Kara <jack@suse.cz>
To: Chris Mason <mason@suse.com>
Cc: reiserfs-list@namesys.com, linux-fsdevel@vger.kernel.org,
George Ronkin <gronkin@nerdvana.com>,
akpm@osdl.org
Subject: Re: [PATCH] Fix quota transaction size
Date: Fri, 20 May 2005 11:44:42 +0200 [thread overview]
Message-ID: <20050520094442.GA8520@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <200505192020.00466.mason@suse.com>
Hello,
> On Thursday 19 May 2005 05:40, Jan Kara wrote:
> > Hello,
> >
> > attached patch improves the estimates on the number of credits needed
> > for a quota operation. This is needed as currently quota overflows the
> > maximum size of a transaction if 1KB blocksize is used. Please apply.
>
> Thanks Jan,
>
> It would make more sense to only allocate for the quota if quotas are
> in use. When you have 10 or more concurrent procs unlinking things,
> they end up waiting for each other because they are trying to reserve
> so many blocks in the transaction. So, a smaller reservation allows
> for better concurrency when quotas are off.
That's a good point. Checking whether the quota is enabled on a
transaction start is probably not a good option as quotas can be turned
on while some transaction is in progress. But we may check whether the
filesystem was mounted with some quota option (better set some
superblock flag when it is so) and reserve a space in a transaction for
quotas in that case. Mount options can be changed only on remounting
which nicely synchronizes everything anyway. And running a filesystem
with quota options but without quota turned on is probably a case
which can suffer some penalty. I'll write the patch for this.
Honza
--
Jan Kara <jack@suse.cz>
SuSE CR Labs
next prev parent reply other threads:[~2005-05-20 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 9:40 [PATCH] Fix quota transaction size Jan Kara
2005-05-20 0:19 ` Chris Mason
2005-05-20 9:44 ` Jan Kara [this message]
2005-05-20 16:20 ` Jan Kara
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=20050520094442.GA8520@atrey.karlin.mff.cuni.cz \
--to=jack@suse.cz \
--cc=akpm@osdl.org \
--cc=gronkin@nerdvana.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mason@suse.com \
--cc=reiserfs-list@namesys.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).