From: jing zhang <zj.barak@gmail.com>
To: tytso@mit.edu
Cc: linux-ext4 <linux-ext4@vger.kernel.org>,
Andreas Dilger <adilger@sun.com>,
Dave Kleikamp <shaggy@linux.vnet.ibm.com>,
"Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [PATCH] ext4: group cache is added in ext4_mb_discard_preallocations()
Date: Wed, 7 Apr 2010 20:50:52 +0800 [thread overview]
Message-ID: <m2yac8f92701004070550zc4b459d3pb33b9d7f5bd875e9@mail.gmail.com> (raw)
In-Reply-To: <20100406183158.GK23670@thunk.org>
2010/4/7, tytso@mit.edu <tytso@mit.edu>:
> On Tue, Mar 30, 2010 at 08:36:17PM +0800, jing zhang wrote:
>> --- linux-2.6.32/fs/ext4/mballoc.c 2009-12-03 11:51:22.000000000 +0800
>> +++ ext4_mm_leak/mballoc-13.c 2010-03-30 20:28:08.000000000 +0800
>> @@ -4183,12 +4183,20 @@ static int ext4_mb_discard_preallocation
>> ext4_group_t i, ngroups = ext4_get_groups_count(sb);
>> int ret;
>> int freed = 0;
>> + static ext4_group_t grp_cache = 0;
>
> This is a problem right there. Remember that there could be multiple
> file systems mounted so a static variable is fundamentally flawed.
>
cool, the static in my patch is a fatal error.
- zj
> In fact, we could have a one filesystem which has more than 3 times
> the number of groups as another file system. I'll leave it as an
> exercise to a reader why your patch would be fundamentally flawed in
> that case.
>
> The other thing to note is that this case only gets hit if the file
> system is so full that we need to empty preallocations. So this means
> hitting this case is rare, which raises two questions: (1) is it worth
> it to optimize this case in the first place (is it really that
> expensive to iterate over all the groups to discard the
> preallocations); (2) can we test this case well?
>
> - Ted
>
prev parent reply other threads:[~2010-04-07 12:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 12:36 [PATCH] ext4: group cache is added in ext4_mb_discard_preallocations() jing zhang
2010-03-30 18:37 ` Aneesh Kumar K. V
2010-03-31 15:10 ` jing zhang
2010-03-31 15:03 ` Andreas Dilger
2010-04-01 12:34 ` jing zhang
2010-04-06 18:49 ` tytso
2010-04-07 12:58 ` jing zhang
2010-04-07 14:46 ` tytso
2010-04-06 18:31 ` tytso
2010-04-07 12:50 ` jing zhang [this message]
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=m2yac8f92701004070550zc4b459d3pb33b9d7f5bd875e9@mail.gmail.com \
--to=zj.barak@gmail.com \
--cc=adilger@sun.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.com \
--cc=tytso@mit.edu \
/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).