From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Florian Heigl <florian.heigl@gmail.com>
Cc: Andrew Xu <xu.an@cloudex.cn>,
xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: [Xen-users] Re: VM disk I/O limit patch
Date: Wed, 22 Jun 2011 09:07:10 -0400 [thread overview]
Message-ID: <20110622130710.GA8216@dumpdata.com> (raw)
In-Reply-To: <BANLkTikGiuOAcyZhOTKpANkHktWMCrtjsw@mail.gmail.com>
On Wed, Jun 22, 2011 at 02:16:09PM +0200, Florian Heigl wrote:
> Hi,
>
> relying on DM is not advisable since this is yet another layer that
> breaks write barriers, plus it kills portability to non-linux OS.
How so? And write barriers don't exist anymore - I think you mean
flush support. And I believe they are fixed now - flush requests
are passed through to the bottom layer (the real disk). But let
me double check that shortly.
Portability to non-linux OS? ? What do you mean by that? As in using
this patch on NetBSD or OpenSolaris backend? The backend in those
OS-es is quite different so it wouldn't be "portable"
>
> btw:
> It would be cool if a block shaping patch finally made it in the Xen
> mainline, since the last one that was submitted in 2009 was apparently
> forgotten...
Why can't dm-ioband do this for you? Hm, I don't remember seeing that patch
at all?
next prev parent reply other threads:[~2011-06-22 13:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 8:29 VM disk I/O limit patch Andrew Xu
2011-06-21 13:33 ` Konrad Rzeszutek Wilk
2011-06-22 12:06 ` [Xen-users] " Andrew Xu
2011-06-22 13:11 ` Konrad Rzeszutek Wilk
2011-06-22 14:12 ` Re[2]: " Andrew Xu
2011-06-22 14:39 ` Konrad Rzeszutek Wilk
2011-06-24 14:29 ` Re[2]: " Ian Jackson
2011-06-22 12:16 ` Re: [Xen-devel] " Florian Heigl
2011-06-22 13:07 ` Konrad Rzeszutek Wilk [this message]
2011-06-23 20:45 ` Shaun Reitan
2011-06-27 15:41 ` Konrad Rzeszutek Wilk
2011-06-27 19:22 ` Shaun Reitan
2011-06-28 11:32 ` Re: [Xen-devel] " Florian Heigl
2011-06-28 13:29 ` [Xen-users] " Konrad Rzeszutek Wilk
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=20110622130710.GA8216@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=florian.heigl@gmail.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
--cc=xu.an@cloudex.cn \
/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.