[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130227213013.GG14253@thunk.org>
Date: Wed, 27 Feb 2013 16:30:13 -0500
From: Theodore Ts'o <tytso@....edu>
To: Dmitry Monakhov <dmonakhov@...nvz.org>
Cc: Dave Jones <davej@...hat.com>,
Markus Trippelsdorf <markus@...ppelsdorf.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"gnehzuil.liu" <gnehzuil.liu@...il.com>,
Zheng Liu <wenqing.lz@...bao.com>,
Borislav Petkov <bp@...en8.de>,
"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] ext4 updates for 3.9
On Thu, Feb 28, 2013 at 12:58:55AM +0400, Dmitry Monakhov wrote:
> Indeed. That's why i give-up rotated disks and run xfstest only on SSD
> or brd module
Note that some problems only show up on slower devices (because then
the race window is wider), and sometimes they only show up on fast
devices. This is why I've been doing runs on both HDD's and on tmpfs
kvm disk image files.
> Later we can simply run xfstest/fio/fsx on this image.
> I'll prepare new xfstest based on that idea. But the only disadvantage
> is that loop dev has bottleneck, all requests will be serialized on i_mutex.
If the image file is used as a disk file for KVM, that should avoid
the serialization bottleneck of using the loop device.
Regards,
- Ted
--
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