From: William Lee Irwin III <wli@holomorphy.com>
To: Alex Tomas <bzzz@tmi.comex.ru>,
linux-kernel <linux-kernel@vger.kernel.org>,
ext2-devel@lists.sourceforge.net, Andrew Morton <akpm@digeo.com>
Subject: Re: [PATCH] distributed counters for ext2 to avoid group scaning
Date: Mon, 17 Mar 2003 01:48:23 -0800 [thread overview]
Message-ID: <20030317094823.GQ20188@holomorphy.com> (raw)
In-Reply-To: <20030317093712.GP20188@holomorphy.com>
On Sun, Mar 16, 2003 at 06:01:55PM +0300, Alex Tomas wrote:
>> ext2 with concurrent balloc/ialloc doesn't maintain global free
>> inodes/blocks counters. this is due to badness of spinlocks and
>> atomic_t from big iron's viewpoint. therefore, to know these values
>> we should scan all group descriptors. there are 81 groups for 10G
>> fs. I believe there is method to avoid scaning and decrease memory
>> footprint.
On Mon, Mar 17, 2003 at 01:37:12AM -0800, William Lee Irwin III wrote:
> benching now
Bad news. I don't have big enough fs's to do this one. Working it...
$ df -HT
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 ext2 4.2G 2.8G 1.2G 72% /
/dev/sdb1 ext2 9.1G 7.0G 1.6G 82% /home
/dev/sdb2 ext2 9.1G 42M 8.6G 1% /results
/dev/sdd1 ext2 19G 8.0G 9.2G 47% /work
/dev/sde1 ext2 19G 1.7G 16G 10% /test
$
-- wli
next prev parent reply other threads:[~2003-03-17 9:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-16 15:01 [PATCH] distributed counters for ext2 to avoid group scaning Alex Tomas
2003-03-16 17:44 ` [Ext2-devel] " Andreas Dilger
2003-03-16 21:55 ` Alex Tomas
2003-03-17 15:11 ` Matthew Wilcox
2003-03-17 15:09 ` Alex Tomas
2003-03-17 15:27 ` Matthew Wilcox
2003-03-17 15:25 ` Alex Tomas
2003-03-17 20:23 ` Andrew Morton
2003-03-17 20:27 ` Matthew Wilcox
2003-03-17 20:40 ` Alex Tomas
2003-03-17 9:37 ` William Lee Irwin III
2003-03-17 9:48 ` William Lee Irwin III [this message]
2003-03-17 10:41 ` Alex Tomas
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=20030317094823.GQ20188@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@digeo.com \
--cc=bzzz@tmi.comex.ru \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@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 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.