From: Christoph Hellwig <hch@infradead.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: hch@infradead.org, Jeremy Fitzhardinge <jeremy@goop.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Vivek Goyal <vgoyal@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Help with implementing some form of barriers in 3.0 kernels.
Date: Thu, 8 Sep 2011 04:08:43 -0400 [thread overview]
Message-ID: <20110908080843.GA14549@infradead.org> (raw)
In-Reply-To: <4E6892B4020000780005536B@nat28.tlf.novell.com>
On Thu, Sep 08, 2011 at 09:02:28AM +0100, Jan Beulich wrote:
> That would need to be done in the backend, as the expectation cannot
> be to patch old frontends to deal with new backends.
Sorry, I meant blkback above.
next prev parent reply other threads:[~2011-09-08 8:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 17:48 Help with implementing some form of barriers in 3.0 kernels Konrad Rzeszutek Wilk
2011-09-07 18:17 ` Vivek Goyal
2011-09-07 18:27 ` Konrad Rzeszutek Wilk
2011-09-07 18:36 ` Vivek Goyal
2011-09-07 20:16 ` Christoph Hellwig
2011-09-07 21:31 ` Vivek Goyal
2011-09-08 8:22 ` Christoph Hellwig
2011-09-08 8:02 ` Jan Beulich
2011-09-08 8:08 ` Christoph Hellwig [this message]
2011-09-13 10:44 ` Jan Beulich
2011-09-14 8:59 ` Konrad Rzeszutek Wilk
2011-09-14 9:12 ` Jan Beulich
2011-09-14 9:30 ` Konrad Rzeszutek Wilk
2011-09-14 10:15 ` Jan Beulich
2011-09-14 14:32 ` Konrad Rzeszutek Wilk
2011-09-14 15:01 ` [PATCH]: xen/blkback: Add support for old BARRIER requests - 'feature-barrier', was "Help with implementing some form of barriers in 3.0 kernels." Konrad Rzeszutek Wilk
2011-09-14 16:13 ` Jan Beulich
2011-09-15 12:51 ` Konrad Rzeszutek Wilk
2011-09-15 13:00 ` Jan Beulich
2011-09-15 14:21 ` Konrad Rzeszutek Wilk
2011-09-15 15:13 ` Jan Kara
2011-09-15 15:15 ` Christoph Hellwig
2011-09-16 9:24 ` Konrad Rzeszutek Wilk
2011-09-15 13:24 ` Jan Kara
2011-09-14 15:34 ` Help with implementing some form of barriers in 3.0 kernels Mike Snitzer
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=20110908080843.GA14549@infradead.org \
--to=hch@infradead.org \
--cc=JBeulich@suse.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox