From: Kashyap Desai <kashyap.desai@broadcom.com>
To: Keith Busch <keith.busch@intel.com>,
Douglas Gilbert <dgilbert@interlog.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Shivasharan Srikanteshwara
<shivasharan.srikanteshwara@broadcom.com>,
Sumit Saxena <sumit.saxena@broadcom.com>,
Peter Rivera <peter.rivera@broadcom.com>,
linux-nvme@lists.infradead.org, linux-scsi@vger.kernel.org
Subject: RE: [PATCH 13/14] megaraid_sas: NVME passthru command support
Date: Wed, 10 Jan 2018 15:02:15 +0530 [thread overview]
Message-ID: <e0eb55ccbcae2640530e43327a7b9aab@mail.gmail.com> (raw)
In-Reply-To: <20180109232305.GH15154@localhost.localdomain>
> -----Original Message-----
> From: Keith Busch [mailto:keith.busch@intel.com]
> Sent: Wednesday, January 10, 2018 4:53 AM
> To: Douglas Gilbert
> Cc: Christoph Hellwig; Kashyap Desai; Shivasharan Srikanteshwara; Sumit
> Saxena; Peter Rivera; linux-nvme@lists.infradead.org; linux-
> scsi@vger.kernel.org
> Subject: Re: [PATCH 13/14] megaraid_sas: NVME passthru command support
>
> On Tue, Jan 09, 2018 at 03:50:44PM -0500, Douglas Gilbert wrote:
> > 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.
>
> What the heck are you talking about? FreeBSD's NVMe passthrough is near
> identical to Linux, and Linux's existed years prior.
>
> You're not even touching the nvme subsystem, so why are you copying the
> linux-nvme mailing list to help you with a non-NVMe device? Please take
your
> ignorant and dubious claims elsewhere.
Keith -
As we discussed for mpt3sas driver NVME driver support, there was request
to add linux-nvme@lists.infradead.org for NVME related discussion.
https://marc.info/?l=linux-kernel&m=149874673729467&w=2
As you mentioned, we are not touching NVME subsystem, we can skip to add
NVME mailing list for future submission w.r.t NVME drive behind MR
(megaraid_sas) and HBA (mpt3sas).
All the NVME drives behind MegaRaid controller is SCSI device irrespective
of transport.
Kashyap
next prev parent reply other threads:[~2018-01-10 9:32 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
2018-01-09 23:23 ` Keith Busch
2018-01-10 9:32 ` Kashyap Desai [this message]
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=e0eb55ccbcae2640530e43327a7b9aab@mail.gmail.com \
--to=kashyap.desai@broadcom.com \
--cc=dgilbert@interlog.com \
--cc=hch@infradead.org \
--cc=keith.busch@intel.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).