From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] NVMe: Skip namespaces with interleaved meta-data
Date: Wed, 28 Jan 2015 15:11:09 +0000 (UTC) [thread overview]
Message-ID: <alpine.LNX.2.00.1501281456010.15481@localhost.lm.intel.com> (raw)
In-Reply-To: <yq1zj93iszd.fsf@sermon.lab.mkp.net>
On Tue, 27 Jan 2015, Martin K. Petersen wrote:
>>>>>> "Keith" == Keith Busch <keith.busch at intel.com> writes:
> Keith,
>
> Keith> I can't register with the blk-integrity extentions until after
> Keith> add_disk is completed because the disk's kobj needs to be
> Keith> initialized before blk_integrity_register. The 'add_disk' itself
> Keith> submits a lot of reads, though. Am I missing something, or how
> Keith> could those succeed when the block device's required integrity
> Keith> format hasn't been setup?
>
> Protection is optional and enabled on a per-I/O basis. Even if the block
> layer's auto protection is enabled it is normal to see a flutter of
> unprotected reads while partitions are being scanned.
Thanks for the info. NVMe doesn't appear to allow disabling metadata
per-io except for a subset of formats. If that's correct, this driver
would have to provide a valid protection buffer for all IO. Checking
with committee comrades for clarification.
next prev parent reply other threads:[~2015-01-28 15:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 18:07 [PATCH] NVMe: Skip namespaces with interleaved meta-data Keith Busch
2015-01-27 21:57 ` David Darrington
2015-01-27 22:09 ` Keith Busch
2015-01-28 1:21 ` Keith Busch
2015-01-28 1:39 ` Martin K. Petersen
2015-01-28 15:11 ` Keith Busch [this message]
2015-01-28 20:50 ` Paul Grabinar
2015-01-28 21:16 ` Keith Busch
2015-01-28 21:46 ` Paul Grabinar
2015-01-28 22:08 ` Martin K. Petersen
2015-01-28 22:17 ` Keith Busch
2015-01-28 22:28 ` Martin K. Petersen
2015-01-29 0:09 ` Keith Busch
2015-01-29 0:57 ` Martin K. Petersen
2015-01-29 15:44 ` Keith Busch
2015-01-30 0:41 ` Martin K. Petersen
2015-01-30 0:57 ` Keith Busch
2015-01-28 22:17 ` Andrey Kuzmin
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=alpine.LNX.2.00.1501281456010.15481@localhost.lm.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