[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <AANLkTikFPQHU78NLfurU1QgeBK07LZD_fEJR2zGyU8ZT@mail.gmail.com>
Date: Thu, 24 Mar 2011 07:19:46 +0200
From: "Amir G." <amir73il@...rs.sourceforge.net>
To: tytso@....edu
Cc: Ext4 Developers List <linux-ext4@...r.kernel.org>,
Yongqiang Yang <xiaoqiangnk@...il.com>
Subject: Re: ext4: removal of alloc_sem locks from block allocation paths
On Wed, Mar 23, 2011 at 11:04 PM, Amir G.
<amir73il@...rs.sourceforge.net> wrote:
> Hi Ted,
>
> I have been running some more tests, including 1K, with no problems observed
Take that back. My test setup was wrong.
xfstest 131 does hit a BUG in ext4_mb_init_cache() with 1K blocks.
I will post a fix when I have it.
> and Yongqiang has also reviewed the patches.
>
> Is there any chance to merge these patches in current merge window?
>
> Thanks,
> Amir.
>
> On Sun, Mar 20, 2011 at 11:32 PM, <amir73il@...rs.sourceforge.net> wrote:
>> The purpose of this patch set is the removal of grp->alloc_sem locks
>> from block allocation paths.
>>
>> This resulting code is cleaner and should perform better in concurrent
>> allocating tasks workloads.
>>
>> I ran several xfstests runs with these patches (4K block only).
>> I tried several online resizes and verifyed that both in-core and on-disk
>> group counters are correct.
>>
>> ext4: move ext4_add_groupblocks() to mballoc.c
>> ext4: implement ext4_add_groupblocks() by freeing blocks
>> ext4: synchronize ext4_mb_init_group() with buddy page lock
>> ext4: teach ext4_mb_init_cache() to skip uptodate buddy caches
>> ext4: remove alloc_semp
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists