linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Douglas Gilbert <dgilbert@interlog.com>
To: Christoph Hellwig <hch@infradead.org>,
	Kashyap Desai <kashyap.desai@broadcom.com>
Cc: Shivasharan Srikanteshwara
	<shivasharan.srikanteshwara@broadcom.com>,
	linux-scsi@vger.kernel.org,
	Sumit Saxena <sumit.saxena@broadcom.com>,
	linux-nvme@lists.infradead.org,
	Peter Rivera <peter.rivera@broadcom.com>
Subject: Re: [PATCH 13/14] megaraid_sas: NVME passthru command support
Date: Tue, 9 Jan 2018 15:50:44 -0500	[thread overview]
Message-ID: <27ebbe5f-e06b-a800-5518-ec63d65d142a@interlog.com> (raw)
In-Reply-To: <20180109164540.GA11861@infradead.org>

On 2018-01-09 11:45 AM, Christoph Hellwig wrote:
> On Tue, Jan 09, 2018 at 10:07:28PM +0530, Kashyap Desai wrote:
>> Chris -
>>
>> Overall NVME support behind MR controller is really a SCSI device. On top
>> of that, for MegaRaid, NVME device can be part of Virtual Disk and those
>> drive will not be exposed to the driver. User application may like to talk
>> to hidden NVME devices (part of VDs). This patch will extend the existing
>> interface for megaraid product in the same way it is currently supported
>> for other protocols like SMP, SATA pass-through.
>>
>> Example - Current smartmon is using megaraid.h (MFI headers) to send SATA
>> pass-through.
>>
>> https://github.com/mirror/smartmontools/blob/master/megaraid.h
> 
> And that is exactly the example of why we should have never allowed
> megaraid any private passthrough ioctls to start with.

Christoph,
Have you tried to do any serious work with <linux/nvme_ioctl.h> and
say compared it with FreeBSD and Microsoft's approach? No prize for
guessing which one is worst (and least extensible). Looks like the
Linux pass-through was at the end of a ToDo list and was "designed"
at 5 a.m in the morning.

RAID cards need a pass-through that allows them to address one of
many physical disks behind the virtual disk presented to OS.
Pass-throughs need to have uncommited room for extra parameters that
will be passed through as-is to the RAID LLD.

So until Christoph gives an example of how that can be done with
<linux/nvme_ioctl.h> then I would like to see Christoph's objection
ignored.


And as a maintainer of smartmontools, I would like to point out that
pretty well all supported RAIDs, on all platforms need specialized
pass-through code. Start by looking at os_linux.cpp and then at the
other OSes. And now smartmontools supports NVMe on most platforms
and at the pass-through level, it is just another one, and not a
particularly clean one.

IMO Intel had their chance on the pass-through front, and blew it.
It is now too late to fix it and that job (impossible ?) should not
fall to MegaRaid maintainers.

Douglas Gilbert

  reply	other threads:[~2018-01-09 20:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 13:35 [PATCH 13/14] megaraid_sas: NVME passthru command support Shivasharan S
2018-01-08 10:05 ` Christoph Hellwig
2018-01-09 16:37   ` Kashyap Desai
2018-01-09 16:45     ` Christoph Hellwig
2018-01-09 20:50       ` Douglas Gilbert [this message]
2018-01-09 23:23         ` Keith Busch
2018-01-10  9:32           ` Kashyap Desai
2018-01-10 10:03         ` Kashyap Desai
2018-01-10 16:22     ` Bart Van Assche
2018-01-10 20:06       ` Douglas Gilbert
2018-01-10 22:14         ` Sathya Prakash Veerichetty
2018-01-11 17:46           ` Keith Busch
2018-01-11 18:07             ` Sathya Prakash Veerichetty
2018-01-15 12:16               ` Kashyap Desai
2018-01-16  3:06                 ` Martin K. Petersen
  -- strict thread matches above, loose matches on Subject: below --
2018-01-05 13:33 Shivasharan S
2018-01-05 13:27 [PATCH 00/14] megaraid_sas: driver updates Shivasharan S
2018-01-05 13:27 ` [PATCH 13/14] megaraid_sas: NVME passthru command support Shivasharan S

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=27ebbe5f-e06b-a800-5518-ec63d65d142a@interlog.com \
    --to=dgilbert@interlog.com \
    --cc=hch@infradead.org \
    --cc=kashyap.desai@broadcom.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=peter.rivera@broadcom.com \
    --cc=shivasharan.srikanteshwara@broadcom.com \
    --cc=sumit.saxena@broadcom.com \
    /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).