From: Chris Mason <mason@suse.com>
To: Jan Kara <jack@suse.cz>
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: Thu, 19 May 2005 20:19:59 -0400 [thread overview]
Message-ID: <200505192020.00466.mason@suse.com> (raw)
In-Reply-To: <20050519094015.GC1871@atrey.karlin.mff.cuni.cz>
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.
-chris
next prev parent reply other threads:[~2005-05-20 0:20 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 [this message]
2005-05-20 9:44 ` Jan Kara
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=200505192020.00466.mason@suse.com \
--to=mason@suse.com \
--cc=akpm@osdl.org \
--cc=gronkin@nerdvana.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--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).