From: paul.grabinar@ranbarg.com (Paul Grabinar)
Subject: [PATCH] NVMe: Skip namespaces with interleaved meta-data
Date: Wed, 28 Jan 2015 21:46:57 +0000 [thread overview]
Message-ID: <54C958D1.3010209@ranbarg.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1501282102210.15481@localhost.lm.intel.com>
On 28/01/15 21:16, Keith Busch wrote:
> I was trying something similar to SCSI, and I think Christoph may
> approve. Instead of all the logic deciding which namespace to attach
> and which to bail, attach all namespaces from NSID 1 to the max, then:
>
> set_capacity(ns->disk, 0);
>
> Wait to initialize the format in nvme_revalidate_disk. If it's a usable
> format, set capacity and sector accordingly, and leave capacity at 0 if
> not. For metadata formats, leave the capacity at 0 until block integrity
> extensions can be registered, then rescan.
What happens if you switch on and off meta-data dynamically with
/sys/block/<bdev>/integrity/write_generate and
/sys/block/<bdev>/integrity/read_verify?
next prev parent reply other threads:[~2015-01-28 21:46 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
2015-01-28 20:50 ` Paul Grabinar
2015-01-28 21:16 ` Keith Busch
2015-01-28 21:46 ` Paul Grabinar [this message]
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=54C958D1.3010209@ranbarg.com \
--to=paul.grabinar@ranbarg.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