linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Kristoffer Knigga <kris@knigga.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm is unable to see Alder Lake IMSM array
Date: Tue, 15 Mar 2022 14:33:38 +0100	[thread overview]
Message-ID: <20220315143338.00000394@linux.intel.com> (raw)
In-Reply-To: <CAKhSdW3v-e6N8GA2Sq=qurACA9S1f5Bsf9pSq6oL1YH4aSR+=g@mail.gmail.com>

On Mon, 14 Mar 2022 09:53:39 -0500
Kristoffer Knigga <kris@knigga.com> wrote:

> Mariusz,
> 
> Thanks for taking a look at this.
> 
> > This is RST family product but mdadm implements VROC solution. Both
> > products have same origin but now they are not aligned and as you
> > can see, they may not be compatible at all.
> 
> Is RST support planned for mdadm?
> 
AFAIK it is not planned.

> > Here we have Sata remapping under VMD controller. I
> > think that our mdadm implementation is not able to handle it
> > correctly, we are assuming that it must be nvme device.
> 
> Out of curiosity, would you expect an array of NVMe devices to work?

We (VROC) relies on efi variables provided by UEFI. If RST UEFI driver
provides them, it will work. We didn't validate such solution so I
cannot be sure. You need to check it yourself.
The simplest way is to run #mdadm --detail-platform. Supported devices
will be listed.

> 
> This kind of programming is far outside of my expertise, but if
> there's anything I can do to help an effort to add this support to
> mdadm, please let me know.  I can provide more information about the
> hardware, and I can build and run tests if that's useful.
> 

I can't take the challenge at this moment, but I won't block adding
such feature in upstream. I can give some suggestions and help
with review.

Thanks,
Mariusz

  reply	other threads:[~2022-03-15 13:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 16:17 mdadm is unable to see Alder Lake IMSM array Kristoffer Knigga
2022-03-14 10:58 ` Mariusz Tkaczyk
2022-03-14 14:53   ` Kristoffer Knigga
2022-03-15 13:33     ` Mariusz Tkaczyk [this message]
2022-03-18 15:34       ` Kristoffer Knigga

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=20220315143338.00000394@linux.intel.com \
    --to=mariusz.tkaczyk@linux.intel.com \
    --cc=kris@knigga.com \
    --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).