linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	"David F." <df7729@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: When will Linux support M2 on RAID ?
Date: Tue, 7 Mar 2017 07:15:28 -0800	[thread overview]
Message-ID: <20170307151528.GA16216@infradead.org> (raw)
In-Reply-To: <a92c6f16-af2d-9d79-fb09-8490aac050db@gmail.com>

On Tue, Mar 07, 2017 at 09:50:22AM -0500, Austin S. Hemmelgarn wrote:
> He's referring to the RAID mode most modern Intel chipsets have, which (last
> I checked) Linux does not support completely and many OEM's are setting by
> default on new systems because it apparently provides better performance
> than AHCI even for a single device.

It actually provides worse performance.  What it does it that it shoves
up to three nvme device bars into the bar of an AHCI device, and
requires the OS to handle them all using a single driver.  The Money's
on crack at Intel decided to do that to provide their "valueable" RSTe
IP (which is a windows ATA + RAID driver in a blob, which now has also
grown a NVMe driver).  The only remotely sane thing is to disable it
in the bios, and burn all people involved with it.  The next best thing
is to provide a fake PCIe root port driver untangling this before it
hits the driver, but unfortunately Intel is unwilling to either do this
on their own or at least provide enough documentation for others to do
it.

  reply	other threads:[~2017-03-07 15:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06  2:09 When will Linux support M2 on RAID ? David F.
2017-03-07  4:52 ` Christoph Hellwig
2017-03-07 14:50   ` Austin S. Hemmelgarn
2017-03-07 15:15     ` Christoph Hellwig [this message]
2017-03-07 15:54       ` Austin S. Hemmelgarn
2017-03-12  0:52         ` David F.
2017-03-07 15:46   ` Dave Jiang

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=20170307151528.GA16216@infradead.org \
    --to=hch@infradead.org \
    --cc=ahferroin7@gmail.com \
    --cc=df7729@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.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).