All of lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH v2 00/13] mpt3sas driver NVMe support:
Date: Tue, 8 Aug 2017 00:04:49 -0400	[thread overview]
Message-ID: <20170808040449.GE842@localhost.localdomain> (raw)
In-Reply-To: <1502120725.2841.28.camel@HansenPartnership.com>

On Mon, Aug 07, 2017@08:45:25AM -0700, James Bottomley wrote:
> On Mon, 2017-08-07@20:01 +0530, Kashyap Desai wrote:
> > 
> > We have to attempt this use case and see how it behaves. I have not
> > tried this, so not sure if things are really bad or just some tuning
> > may be helpful. I will revert back to you on this.
> > 
> > I understood request as -??We need some udev rules to be working well
> > for *same* NVME drives if it is behind <mpt3sas> or native <nvme>.
> > Example - If user has OS installed on NVME drive which is behind
> > <mpt3sas> driver as SCSI disk should be able to boot if he/she hooked
> > same NVME drive which is detected by native <nvme> driver (and vice
> > versa.)
> 
> It's not just the udev rules, it's the tools as well; possibly things
> like that nvme-cli toolkit Intel is doing.

It looks like they can make existing nvme tooling work with little
effort if they have the driver implement NVME_IOCTL_ADMIN_COMMAND, and
then have their driver build the MPI NVMe Encapsulated Request from that.

WARNING: multiple messages have this Message-ID (diff)
From: Keith Busch <keith.busch@intel.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Kashyap Desai <kashyap.desai@broadcom.com>,
	Christoph Hellwig <hch@infradead.org>,
	Hannes Reinecke <hare@suse.de>,
	Sreekanth Reddy <sreekanth.reddy@broadcom.com>,
	linux-scsi@vger.kernel.org,
	Chaitra Basappa <chaitra.basappa@broadcom.com>,
	Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>,
	Sathya Prakash Veerichetty <sathya.prakash@broadcom.com>,
	linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
	martin.petersen@oracle.com
Subject: Re: [PATCH v2 00/13] mpt3sas driver NVMe support:
Date: Tue, 8 Aug 2017 00:04:49 -0400	[thread overview]
Message-ID: <20170808040449.GE842@localhost.localdomain> (raw)
In-Reply-To: <1502120725.2841.28.camel@HansenPartnership.com>

On Mon, Aug 07, 2017 at 08:45:25AM -0700, James Bottomley wrote:
> On Mon, 2017-08-07 at 20:01 +0530, Kashyap Desai wrote:
> > 
> > We have to attempt this use case and see how it behaves. I have not
> > tried this, so not sure if things are really bad or just some tuning
> > may be helpful. I will revert back to you on this.
> > 
> > I understood request as -  We need some udev rules to be working well
> > for *same* NVME drives if it is behind <mpt3sas> or native <nvme>.
> > Example - If user has OS installed on NVME drive which is behind
> > <mpt3sas> driver as SCSI disk should be able to boot if he/she hooked
> > same NVME drive which is detected by native <nvme> driver (and vice
> > versa.)
> 
> It's not just the udev rules, it's the tools as well; possibly things
> like that nvme-cli toolkit Intel is doing.

It looks like they can make existing nvme tooling work with little
effort if they have the driver implement NVME_IOCTL_ADMIN_COMMAND, and
then have their driver build the MPI NVMe Encapsulated Request from that.

  reply	other threads:[~2017-08-08  4:04 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14 13:22 [PATCH v2 00/13] mpt3sas driver NVMe support: Suganath Prabu S
2017-07-14 13:22 ` Suganath Prabu S
2017-07-14 13:22 ` [PATCH v2 01/13] mpt3sas: Update MPI Header Suganath Prabu S
2017-07-14 13:22   ` Suganath Prabu S
2017-08-03  6:24   ` Hannes Reinecke
2017-08-03  6:24     ` Hannes Reinecke
2017-08-03  7:55     ` Johannes Thumshirn
2017-08-03  7:55       ` Johannes Thumshirn
2017-08-03  9:34       ` Sreekanth Reddy
2017-08-03  9:34         ` Sreekanth Reddy
2017-07-14 13:22 ` [PATCH v2 02/13] mpt3sas: Add nvme device support in slave alloc, target alloc and probe Suganath Prabu S
2017-07-14 13:22   ` Suganath Prabu S
2017-08-03  6:27   ` Hannes Reinecke
2017-08-03  6:27     ` Hannes Reinecke
2017-08-03 10:09     ` Sreekanth Reddy
2017-08-03 10:09       ` Sreekanth Reddy
2017-07-14 13:22 ` [PATCH v2 03/13] mpt3sas: SGL to PRP Translation for I/Os to NVMe devices Suganath Prabu S
2017-07-14 13:22   ` Suganath Prabu S
2017-07-27 13:26   ` Martin K. Petersen
2017-07-27 13:26     ` Martin K. Petersen
2017-07-14 13:22 ` [PATCH v2 04/13] mpt3sas: Added support for nvme encapsulated request message Suganath Prabu S
2017-07-14 13:22   ` Suganath Prabu S
2017-08-03  6:33   ` Hannes Reinecke
2017-08-03  6:33     ` Hannes Reinecke
2017-07-14 13:22 ` [PATCH v2 05/13] mpt3sas: API 's to support NVMe drive addition to SML Suganath Prabu S
2017-07-14 13:22   ` Suganath Prabu S
2017-08-03  6:35   ` Hannes Reinecke
2017-08-03  6:35     ` Hannes Reinecke
2017-07-14 13:22 ` [PATCH v2 06/13] mpt3sas: API's to remove nvme drive from sml Suganath Prabu S
2017-07-14 13:22   ` Suganath Prabu S
2017-08-03  6:36   ` Hannes Reinecke
2017-08-03  6:36     ` Hannes Reinecke
2017-07-14 13:22 ` [PATCH v2 07/13] mpt3sas: Handle NVMe PCIe device related events generated from firmware Suganath Prabu S
2017-07-14 13:22   ` Suganath Prabu S
2017-08-03  6:38   ` Hannes Reinecke
2017-08-03  6:38     ` Hannes Reinecke
2017-07-14 13:22 ` [PATCH v2 08/13] mpt3sas: Set NVMe device queue depth as 128 Suganath Prabu S
2017-07-14 13:22   ` Suganath Prabu S
2017-08-03  6:39   ` Hannes Reinecke
2017-08-03  6:39     ` Hannes Reinecke
2017-08-03  9:52     ` Sreekanth Reddy
2017-08-03  9:52       ` Sreekanth Reddy
2017-07-14 13:22 ` [PATCH v2 09/13] mpt3sas: scan and add nvme device after controller reset Suganath Prabu S
2017-07-14 13:22   ` Suganath Prabu S
2017-08-03  6:40   ` Hannes Reinecke
2017-08-03  6:40     ` Hannes Reinecke
2017-08-03 10:19     ` Sreekanth Reddy
2017-08-03 10:19       ` Sreekanth Reddy
2017-07-14 13:22 ` [PATCH v2 10/13] mpt3as: Add-Task-management-debug-info-for-NVMe-drives Suganath Prabu S
2017-07-14 13:22   ` Suganath Prabu S
2017-08-03  6:43   ` Hannes Reinecke
2017-08-03  6:43     ` Hannes Reinecke
2017-07-14 13:22 ` [PATCH v2 11/13] mpt3sas: NVMe drive support for BTDHMAPPING ioctl command and log info Suganath Prabu S
2017-07-14 13:22   ` Suganath Prabu S
2017-08-03  6:44   ` Hannes Reinecke
2017-08-03  6:44     ` Hannes Reinecke
2017-07-14 13:22 ` [PATCH v2 12/13] mpt3sas: Fix nvme drives checking for tlr Suganath Prabu S
2017-07-14 13:22   ` Suganath Prabu S
2017-08-03  6:44   ` Hannes Reinecke
2017-08-03  6:44     ` Hannes Reinecke
2017-07-14 13:22 ` [PATCH v2 13/13] mpt3sas: Update mpt3sas driver version Suganath Prabu S
2017-07-14 13:22   ` Suganath Prabu S
2017-08-03  6:45   ` Hannes Reinecke
2017-08-03  6:45     ` Hannes Reinecke
2017-07-25  5:20 ` [PATCH v2 00/13] mpt3sas driver NVMe support: Suganath Prabu Subramani
2017-07-25  5:20   ` Suganath Prabu Subramani
2017-08-02  8:14 ` Hannes Reinecke
2017-08-02  8:14   ` Hannes Reinecke
2017-08-03  6:48   ` Hannes Reinecke
2017-08-03  6:48     ` Hannes Reinecke
2017-08-05 13:53   ` Christoph Hellwig
2017-08-05 13:53     ` Christoph Hellwig
2017-08-05 14:42     ` James Bottomley
2017-08-05 14:42       ` James Bottomley
2017-08-07 13:56       ` Kashyap Desai
2017-08-07 13:56         ` Kashyap Desai
2017-08-07 14:18         ` James Bottomley
2017-08-07 14:18           ` James Bottomley
2017-08-07 14:31           ` Kashyap Desai
2017-08-07 14:31             ` Kashyap Desai
2017-08-07 15:45             ` James Bottomley
2017-08-07 15:45               ` James Bottomley
2017-08-08  4:04               ` Keith Busch [this message]
2017-08-08  4:04                 ` Keith Busch
2017-08-08  7:03                 ` Sreekanth Reddy
2017-08-08  7:03                   ` Sreekanth Reddy
2017-08-08  7:29                   ` Keith Busch
2017-08-08  7:29                     ` Keith Busch

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=20170808040449.GE842@localhost.localdomain \
    --to=keith.busch@intel.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 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.