From: Alex <alex@bpmit.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: KVM on top of BTRFS
Date: Tue, 12 Jun 2012 15:45:26 +0000 (UTC) [thread overview]
Message-ID: <loom.20120612T174347-287@post.gmane.org> (raw)
In-Reply-To: loom.20120612T162801-407@post.gmane.org
Alex <alex <at> bpmit.com> writes:
>
> Roman Mamedov <rm <at> romanrm.ru> writes:
>
> (Machine has no other load at all)
>
>
Roman Mamedov didn't write it, I did, I had huge trouble getting past the 80
char limit thing! Sorry Roman.
next prev parent reply other threads:[~2012-06-12 15:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 23:22 KVM on top of BTRFS Matthew Hawn
2012-06-11 23:53 ` Alex
2012-06-12 1:08 ` dima
2012-06-12 7:33 ` Roman Mamedov
2012-06-12 15:39 ` Alex
2012-06-12 15:45 ` Alex [this message]
2012-06-12 20:33 ` steamraven
2012-06-13 21:42 ` Ernst Sjöstrand
2012-06-13 21:47 ` steamraven
2012-06-15 20:10 ` steamraven
2012-06-12 14:48 ` Hubert Kario
2012-06-12 15:43 ` Alex
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=loom.20120612T174347-287@post.gmane.org \
--to=alex@bpmit.com \
--cc=linux-btrfs@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox