From: Keith Busch <keith.busch@intel.com>
To: "Matias Bjørling" <m@bjorling.me>
Cc: thornber@redhat.com, snitzer@redhat.com, hch@infradead.org,
hayakawa@valinux.co.jp, axboe@fb.com, andy@rudoff.com,
dm-devel@redhat.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, bvanassche@acm.org,
linux-nvme@lists.infradead.org, jmad@itu.dk
Subject: Re: [PATCH 4/5] lightnvm: NVMe integration
Date: Wed, 8 Oct 2014 10:13:48 -0600 (MDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1410081004310.4688@AMR> (raw)
In-Reply-To: <1412783736-18115-5-git-send-email-m@bjorling.me>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 436 bytes --]
On Wed, 8 Oct 2014, Matias Bjørling wrote:
> NVMe devices are identified by the vendor specific bits:
>
> Bit 3 in OACS (device-wide). Currently made per device, as the nvme
> namespace is missing in the completion path.
The NVM-Express 1.2 actually defined this bit for Namespace Management,
so I don't think we can use bits the spec marked as "reserved". Maybe
you can trigger off some vendor specific Command Set Supported instead.
next prev parent reply other threads:[~2014-10-08 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 15:55 [PATCH 0/5] Support for Open-Channel SSDs (was dm-lightnvm) Matias Bjørling
2014-10-08 15:55 ` [PATCH 1/5] NVMe: Convert to blk-mq Matias Bjørling
2014-10-08 15:55 ` [PATCH 2/5] block: extend rq_flag_bits Matias Bjørling
2014-10-08 15:55 ` [PATCH 3/5] lightnvm: Support for Open-Channel SSDs Matias Bjørling
2014-10-08 15:55 ` [PATCH 4/5] lightnvm: NVMe integration Matias Bjørling
2014-10-08 16:13 ` Keith Busch [this message]
2014-10-08 15:55 ` [PATCH 5/5] lightnvm: null_blk integration Matias Bjørling
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.LRH.2.03.1410081004310.4688@AMR \
--to=keith.busch@intel.com \
--cc=andy@rudoff.com \
--cc=axboe@fb.com \
--cc=bvanassche@acm.org \
--cc=dm-devel@redhat.com \
--cc=hayakawa@valinux.co.jp \
--cc=hch@infradead.org \
--cc=jmad@itu.dk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=m@bjorling.me \
--cc=snitzer@redhat.com \
--cc=thornber@redhat.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