From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH v2 0/7] NVMe Data Integrity Extensions
Date: Thu, 21 Mar 2013 11:52:00 -0600 [thread overview]
Message-ID: <1363888327-7420-1-git-send-email-keith.busch@intel.com> (raw)
This patch set adds data integrity extensions to NVMe. Contrast with
the previous patch attempt, this makes some modifications to sd_dif
to export the template so a block driver can make use of it instead of
copying it. There are more namespace block formats possible than what is
available in SCSI, so I had to make some modifications to the integrity
code to take this into account. I hope that's okay.
Keith Busch (7):
sd: remove invalid ref tag check
sd: skip verifying unwritten sectors
sd: hw sector size calculation
sd: arbitrary dif meta-data sizes
sd: export dif integrity template
NVMe: Split non-mergeable bio requests
NVMe: End-to-end data protection
drivers/block/nvme.c | 277 ++++++++++++++++++++++++++++++++++++++++++------
drivers/scsi/sd_dif.c | 144 ++++++++++++++++---------
fs/bio-integrity.c | 19 ++--
include/linux/blkdev.h | 10 ++-
include/linux/nvme.h | 28 ++++-
5 files changed, 378 insertions(+), 100 deletions(-)
next reply other threads:[~2013-03-21 17:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 17:52 Keith Busch [this message]
2013-03-21 17:52 ` [PATCH v2 1/7] sd: remove invalid ref tag check Keith Busch
2013-03-21 17:52 ` [PATCH v2 2/7] sd: skip verifying unwritten sectors Keith Busch
2013-03-21 17:52 ` [PATCH v2 3/7] sd: hw sector size calculation Keith Busch
2013-03-21 17:52 ` [PATCH v2 4/7] sd: arbitrary dif meta-data sizes Keith Busch
2013-03-21 17:52 ` [PATCH v2 5/7] sd: export dif integrity template Keith Busch
2013-03-21 17:52 ` [PATCH v2 6/7] NVMe: Split non-mergeable bio requests Keith Busch
2013-03-21 17:52 ` [PATCH v2 7/7] NVMe: End-to-end data protection Keith Busch
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=1363888327-7420-1-git-send-email-keith.busch@intel.com \
--to=keith.busch@intel.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).