Re: [PATCH 0/4] (RESEND) ext3[34] barrier changes
- From: Jamie Lokier <jamie@xxxxxxxxxxxxx>
- Date: Tue, 20 May 2008 15:42:34 +0100
Ric Wheeler wrote:
I will have to figure out to get this kind of test going without all
of my big EMC toys ;-)
Fwiw, you can test correctness by running a nested VM-in-VM guest
which simulates disk write cache and flush operations (which flush to
the host kernel). I believe recent QEMU/KVM has this as an option.
Data written by the innermost guest will reside in the middle kernel's
write cache.
Disk cache flush commands from the innermost kernel will cause the
middle kernel to write dirty sectors to the outer kernel. Killing the
outermost host process is roughly equivalent to pulling the plug on a
real machine, but faster and without hurting real hardware.
This might not tell you much about performance, but you should be able
to run a lot of repeatable filesystem barrier tests this way.
-- Jamie
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH 0/4] (RESEND) ext3[34] barrier changes
- From: Eric Sandeen
- Re: [PATCH 0/4] (RESEND) ext3[34] barrier changes
- From: Theodore Tso
- Re: [PATCH 0/4] (RESEND) ext3[34] barrier changes
- From: Andrew Morton
- Re: [PATCH 0/4] (RESEND) ext3[34] barrier changes
- From: Chris Mason
- Re: [PATCH 0/4] (RESEND) ext3[34] barrier changes
- From: Theodore Tso
- Re: [PATCH 0/4] (RESEND) ext3[34] barrier changes
- From: Ric Wheeler
- [PATCH 0/4] (RESEND) ext3[34] barrier changes
- Prev by Date: Re: [X86] Add a boot parameter to force-enable PAT
- Next by Date: Re: [PATCH 1/8] Scaling msgmni to the amount of lowmem
- Previous by thread: Re: [PATCH 0/4] (RESEND) ext3[34] barrier changes
- Next by thread: Re: [PATCH 0/4] (RESEND) ext3[34] barrier changes
- Index(es):
Relevant Pages
|
