[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51352C1C.40409@sgi.com>
Date: Mon, 4 Mar 2013 17:19:56 -0600
From: Rich Johnston <rjohnston@....com>
To: Dmitry Monakhov <dmonakhov@...nvz.org>
CC: <xfs@....sgi.com>, <linux-fsdevel@...r.kernel.org>,
<linux-ext4@...r.kernel.org>, <dchinner@...hat.com>
Subject: Re: [PATCH 09/10] xfstest: add defragmentation stress tests for ext4
On 03/01/2013 07:30 PM, Dmitry Monakhov wrote:
> On Fri, 1 Mar 2013 13:23:50 -0600, Rich Johnston <rjohnston@....com> wrote:
>> On 02/20/2013 04:42 AM, Dmitry Monakhov wrote:
>>
>> Let me know if you agree with these changes and I will make them at
>> commit time.
> Yes, please do.
>>
>> Thanks
>> --Rich
commit a3d92a6cbdf9e98d8e256974b50b025d1d4575ec
Author: Dmitry Monakhov <dmonakhov@...nvz.org>
Date: Wed Feb 20 10:42:14 2013 +0000
xfstest: add defragmentation stress tests for ext4
Perform various regression tests for ext4defrag subsystem
301'th Test1: Defragment file while other task does direct AIO
302'th Test2: Perform defragmentation on file under buffered AIO
while third task does direct AIO to donor file
303'th Test3: Two defrag tasks use common donor file.
304'th Test4: Stress defragmentation. Several threads perform
fragmentation at random position use inplace=1 will
allocate and free blocks inside defrag event improve
load pressure.
This tests are considered dangerous because 302'th and 303'th are known
to trigger OOPS on recent kernels
see:https://gist.github.com/dmonakhov/4770
294
--
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