From: Peter Hurley <peter@hurleysoftware.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Hugo Mills <hugo@carfax.org.uk>,
Nick Krause <xerofoify@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Work Queue for btrfs compression writes
Date: Wed, 30 Jul 2014 10:36:57 -0400 [thread overview]
Message-ID: <53D90309.9070909@hurleysoftware.com> (raw)
In-Reply-To: <20140730141329.GC20353@thunk.org>
On 07/30/2014 10:13 AM, Theodore Ts'o wrote:
> On Wed, Jul 30, 2014 at 10:38:21AM +0100, Hugo Mills wrote:
>> qemu/kvm is good for this, because it has a mode
>> that bypasses the BIOS and bootloader emulation, and just directly
>> runs a kernel from a file on the host machine. This is fast. You can
>> pass large sparse files to the VM to act as scratch disks, plus keep
>> another smaller file for the guest OS (and a copy of it so that you
>> can throw one away and make another one quickly and easily).
>
> Nick,
>
> The xfstests-bld/kvm-xfstests git tree I pointed out to you has an
> example of a test infrastructure which does this for ext4. It's been
> on my todo list to support other file systems, and I have some plans
> for how to do thi, but it's been low on my priority list. If someone
> in the btrfs development community is interested in working with me on
> this, they should contact me.
Ted,
Where is that git tree? I've been planning to set up a unit test and
regression suite for tty/serial, and wouldn't mind cribbing the
infrastructure from someone's existing work.
Regards,
Peter Hurley
next prev parent reply other threads:[~2014-07-30 15:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 3:54 Work Queue for btrfs compression writes Nick Krause
[not found] ` <CA+WRLO9HdX=PDktUci2bQNM0Wp6DsjxiiWBNAxOtvitPqWDCAg@mail.gmail.com>
2014-07-30 4:54 ` Nick Krause
2014-07-31 3:14 ` Austin S Hemmelgarn
2014-07-31 3:32 ` Nick Krause
2014-07-30 9:38 ` Hugo Mills
2014-07-30 14:13 ` Theodore Ts'o
2014-07-30 14:36 ` Peter Hurley [this message]
2014-07-31 11:35 ` Theodore Ts'o
2014-07-30 15:36 ` ashford
2014-07-30 17:19 ` Nick Krause
2014-07-30 18:31 ` ashford
2014-07-30 19:40 ` Nick Krause
2014-08-04 13:29 ` Chris Mason
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=53D90309.9070909@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=xerofoify@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.