All of lore.kernel.org
 help / color / mirror / Atom feed
From: martin.petersen@oracle.com (Martin K. Petersen)
Subject: Partitions and end-to-end protection
Date: Tue, 14 Jul 2015 14:58:17 -0400	[thread overview]
Message-ID: <yq11tgash12.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20150714184344.GA29437@infradead.org> (Christoph Hellwig's message of "Tue, 14 Jul 2015 11:43:44 -0700")

>>>>> "Christoph" == Christoph Hellwig <hch at infradead.org> writes:

>> The gendisk is a prerequisite by virtue of the integrity profile
>> hanging off of it.

Christoph> Having one allocated is.  But why do we need to have it added
Christoph> (at which point it is live)?

Well, we're poking at the queue (for block size) and the bdi. I guess we
could split things up and have another function to twiddle these
parameters separately. During revalidate, perhaps.

But the fundamental question remains: Why is it a prerequisite for the
NVMe integrity profile to be added before the disk is live? Nobody else
requires this (sd, md, dm).

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2015-07-14 18:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 18:50 Partitions and end-to-end protection Paul Grabinar
2015-07-13 19:16 ` Keith Busch
2015-07-13 19:22   ` Paul Grabinar
2015-07-14 18:06   ` Christoph Hellwig
2015-07-14 18:13     ` Dan Williams
2015-07-14 18:15       ` Christoph Hellwig
2015-07-14 18:25         ` Dan Williams
2015-07-14 18:41     ` Martin K. Petersen
2015-07-14 18:43       ` Christoph Hellwig
2015-07-14 18:58         ` Martin K. Petersen [this message]
2015-07-14 19:25           ` Keith Busch
2015-07-14 19:38             ` Martin K. Petersen
2015-07-14 19:45               ` Keith Busch
2015-07-14 20:07                 ` Martin K. Petersen
2015-07-14 20:14                   ` 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=yq11tgash12.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.