| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20170307151528.GA16216@infradead.org>
Date: Tue, 7 Mar 2017 07:15:28 -0800
From: Christoph Hellwig <hch@...radead.org>
To: "Austin S. Hemmelgarn" <ahferroin7@...il.com>
Cc: Christoph Hellwig <hch@...radead.org>,
"David F." <df7729@...il.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
"linux-raid@...r.kernel.org" <linux-raid@...r.kernel.org>
Subject: Re: When will Linux support M2 on RAID ?
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.
Powered by blists - more mailing lists