From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: linux-kernel@vger.kernel.org
Cc: axboe@kernel.dk, xen-devel@lists.xensource.com,
jeremy.fitzhardinge@citrix.com, JBeulich@novell.com
Subject: [PATCH] xen-blk[front|back] FUA additions.
Date: Fri, 9 Sep 2011 14:30:58 -0400 [thread overview]
Message-ID: <1315593060-20031-1-git-send-email-konrad.wilk@oracle.com> (raw)
I am proposing these two patches for 3.2. They allow the backend
to process the REQ_FUA request as well. Previous to these patches
it only did REQ_FLUSH. There is also a bug-fix for the logic
of how barrier/flushes were handled.
The patches are based on a branch which also has 'feature-discard'
patches, so they won't apply nativly on top of 3.1-rc5.
Please review and if there are no concerns I will send a proper
git pull to Jens to pick up the whole branch for 3.2.
drivers/block/xen-blkback/blkback.c | 11 ++++++-----
drivers/block/xen-blkfront.c | 12 ++++++------
drivers/block/xen-blkfront.c | 8 ++++----
3 files changed, 16 insertions(+), 15 deletions(-)
The full git tree is currently at my backup git tree:
git://oss.oracle.com/git/kwilk/xen.git stable/for-jens-3.2
next reply other threads:[~2011-09-09 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 18:30 Konrad Rzeszutek Wilk [this message]
2011-09-09 18:30 ` [PATCH 1/3] xen/blk[front|back]: Use the full FLUSH | FUA instead of just FLUSH Konrad Rzeszutek Wilk
2011-09-10 18:08 ` Christoph Hellwig
2011-09-11 0:33 ` Konrad Rzeszutek Wilk
2011-09-09 18:31 ` [PATCH 3/3] xen-blkfront: If no barrier or flush is supported, use invalid operation Konrad Rzeszutek Wilk
2011-09-12 8:01 ` Jan Beulich
2011-09-16 19:15 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-09-19 9:35 ` Jan Beulich
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=1315593060-20031-1-git-send-email-konrad.wilk@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@novell.com \
--cc=axboe@kernel.dk \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).