All of lore.kernel.org
 help / color / mirror / Atom feed
From: martin.petersen@oracle.com (Martin K. Petersen)
Subject: [PATCH 0/2] NVMe 1.4 Identify Namespace Support
Date: Fri, 07 Jun 2019 11:21:16 -0400	[thread overview]
Message-ID: <yq1a7etjuab.fsf@oracle.com> (raw)
In-Reply-To: <CAOSXXT5vsi4Fp20dj9TrouwNAYfOAMxAsbFZADZQ9pZE8uo3VA@mail.gmail.com> (Keith Busch's message of "Fri, 7 Jun 2019 07:56:21 -0600")


Keith,

> Series looks good. There doesn't seem to be much in-kernel use for
> these preferred access attributes unfortunately, but this is a good
> start.

Userland makes use of them to ensure partition/MD/DM alignment, pick
sane values for filesystem layout, etc.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2019-06-07 15:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06 21:28 [PATCH 0/2] NVMe 1.4 Identify Namespace Support Bart Van Assche
2019-06-06 21:28 ` [PATCH 1/2] nvme: Introduce NVMe 1.4 Identify Namespace fields in struct nvme_id_ns Bart Van Assche
2019-06-06 21:40   ` Chaitanya Kulkarni
2019-06-07 15:18   ` Martin K. Petersen
2019-06-06 21:28 ` [PATCH 2/2] nvme: Set physical block size and optimal I/O size according to NVMe 1.4 Bart Van Assche
2019-06-06 21:42   ` Chaitanya Kulkarni
2019-06-06 21:48     ` Bart Van Assche
2019-06-06 21:58       ` Chaitanya Kulkarni
2019-06-07 16:42       ` Christoph Hellwig
2019-06-07 15:19   ` Martin K. Petersen
2019-06-07 16:42   ` Christoph Hellwig
2019-06-07 13:56 ` [PATCH 0/2] NVMe 1.4 Identify Namespace Support Keith Busch
2019-06-07 15:21   ` Martin K. Petersen [this message]
2019-06-07 16:26     ` Keith Busch
2019-06-07 16:44       ` 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=yq1a7etjuab.fsf@oracle.com \
    --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.