All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Christoph Hellwig <hch@infradead.org>, "David F." <df7729@gmail.com>
Cc: 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 09:50:22 -0500	[thread overview]
Message-ID: <a92c6f16-af2d-9d79-fb09-8490aac050db@gmail.com> (raw)
In-Reply-To: <20170307045200.GA1708@infradead.org>

On 2017-03-06 23:52, Christoph Hellwig wrote:
> On Sun, Mar 05, 2017 at 06:09:42PM -0800, David F. wrote:
>> More and more systems are coming with M2 on RAID and Linux doesn't
>> work unless you change the system out of RAID mode.  This is becoming
>> more and more of a problem.   What is the status of Linux support for
>> the new systems?
>
> Your message doesn't make sense at all.  MD works on absolutely any
> Linux block device, and I've used it on plenty M.2 form factor devices -
> not that the form factor has anything to do with how Linux would treat
> a device.
>
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.  The bigger issue with 
this is that it's damn near impossible to get to the firmware on many 
new systems, and even if you can, some OEM's aren't even giving the 
option to use AHCI mode instead of the RAID mode.

The whole M.2 thing is absolutely bogus though, my thought is that 
people are conflating the two because this switch to using RAID mode by 
default is happening concurrently with a general movement towards using 
M.2 devices as primary storage.

  reply	other threads:[~2017-03-07 14:50 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 [this message]
2017-03-07 15:15     ` Christoph Hellwig
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=a92c6f16-af2d-9d79-fb09-8490aac050db@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=df7729@gmail.com \
    --cc=hch@infradead.org \
    --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 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.