[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d411baa1bdd34f1a1289480d13fe1cef@mail.gmail.com>
Date: Fri, 14 Jun 2019 01:34:00 +0530
From: Kashyap Desai <kashyap.desai@...adcom.com>
To: Christoph Hellwig <hch@....de>
Cc: Jens Axboe <axboe@...nel.dk>, Sebastian Ott <sebott@...ux.ibm.com>,
Sagi Grimberg <sagi@...mberg.me>,
Max Gurtovoy <maxg@...lanox.com>,
Bart Van Assche <bvanassche@....org>,
Ulf Hansson <ulf.hansson@...aro.org>,
Alan Stern <stern@...land.harvard.edu>,
Oliver Neukum <oneukum@...e.com>, linux-block@...r.kernel.org,
linux-rdma@...r.kernel.org, linux-mmc@...r.kernel.org,
linux-nvme@...ts.infradead.org, linux-scsi@...r.kernel.org,
"PDL,MEGARAIDLINUX" <megaraidlinux.pdl@...adcom.com>,
PDL-MPT-FUSIONLINUX <mpt-fusionlinux.pdl@...adcom.com>,
linux-hyperv@...r.kernel.org, linux-usb@...r.kernel.org,
usb-storage@...ts.one-eyed-alien.net, linux-kernel@...r.kernel.org
Subject: RE: [PATCH 10/13] megaraid_sas: set virt_boundary_mask in the scsi host
>
> So before I respin this series, can you help with a way to figure out
for
> mpt3sas and megaraid if a given controller supports NVMe devices at all,
so
> that we don't have to set the virt boundary if not?
In MegaRaid we have below enum - VENTURA_SERIES and AERO_SERIES
supports NVME
enum MR_ADAPTER_TYPE {
MFI_SERIES = 1,
THUNDERBOLT_SERIES = 2,
INVADER_SERIES = 3,
VENTURA_SERIES = 4,
AERO_SERIES = 5,
};
In mpt3sas driver we have below method - If IOC FACT reports NVME Device
support in Protocol Flags, we can consider it as HBA with NVME drive
support.
ioc->facts.ProtocolFlags & MPI2_IOCFACTS_PROTOCOL_NVME_DEVICES
Kashyap
Powered by blists - more mailing lists