From: hch@infradead.org (Christoph Hellwig)
Subject: Linux-nvme Digest, Vol 56, Issue 64
Date: Fri, 2 Dec 2016 05:28:15 -0800 [thread overview]
Message-ID: <20161202132815.GA14982@infradead.org> (raw)
In-Reply-To: <20161128163600.GD2609@localhost.localdomain>
On Mon, Nov 28, 2016@11:36:00AM -0500, Keith Busch wrote:
> If I understand correctly what you're using, you'll want to use the
> BIOS's AHCI mode for Linux so that the NVMe device is not remapped into
> the "RAID" device.
Yes, what a great terminology choice by the Chipset and BIOS people.
I think we'll need a patch to the ahci driver at leat to warn about
remapped device.
prev parent reply other threads:[~2016-12-02 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3.1480276802.9433.linux-nvme@lists.infradead.org>
2016-11-28 4:57 ` Linux-nvme Digest, Vol 56, Issue 64 Efrem Mc
2016-11-28 16:36 ` Keith Busch
2016-12-02 13:28 ` Christoph Hellwig [this message]
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=20161202132815.GA14982@infradead.org \
--to=hch@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).