From: axboe@fb.com (Jens Axboe)
Subject: [PATCH] NVMe: Fix IO for extended metadata formats
Date: Fri, 19 Jun 2015 13:16:51 -0600 [thread overview]
Message-ID: <55846AA3.7060701@fb.com> (raw)
In-Reply-To: <1434733650-16440-1-git-send-email-keith.busch@intel.com>
On 06/19/2015 11:07 AM, Keith Busch wrote:
> This fixes io submit ioctl handling when using extended metadata
> formats. When these formats are used, the user provides a single virtually
> contiguous buffer containing both the block and metadata interleaved,
> so the metadata size needs to be added to the total length and not mapped
> as a separate transfer.
>
> The command is also driver generated, so this patch does not enforce
> blk-integrity extensions provide the metadata buffer.
Applied for 4.2.
--
Jens Axboe
next prev parent reply other threads:[~2015-06-19 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 17:07 [PATCH] NVMe: Fix IO for extended metadata formats Keith Busch
2015-06-19 19:16 ` Jens Axboe [this message]
2015-06-22 5:34 ` Christoph Hellwig
2015-06-22 15:17 ` Busch, Keith
2015-06-22 15:39 ` Christoph Hellwig
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=55846AA3.7060701@fb.com \
--to=axboe@fb.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