All of lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 13/14] megaraid_sas: NVME passthru command support
Date: Thu, 11 Jan 2018 10:46:20 -0700	[thread overview]
Message-ID: <20180111174619.GA2860@localhost.localdomain> (raw)
In-Reply-To: <e407e98c266c060412bfa8b64ded18df@mail.gmail.com>

On Wed, Jan 10, 2018@03:14:40PM -0700, Sathya Prakash Veerichetty wrote:
> In the case of RAID controllers, all of those drives and RAID volumes
> are exposed to the OS as generic SCSI devices

So even when used as a RAID member, there will be a device handle at
/dev/sdX for each NVMe device the megaraid controller manages?

WARNING: multiple messages have this Message-ID (diff)
From: Keith Busch <keith.busch@intel.com>
To: Sathya Prakash Veerichetty <sathya.prakash@broadcom.com>
Cc: dgilbert@interlog.com, Bart Van Assche <Bart.VanAssche@wdc.com>,
	hch@infradead.org, Kashyap Desai <kashyap.desai@broadcom.com>,
	Shivasharan Srikanteshwara
	<shivasharan.srikanteshwara@broadcom.com>,
	Sumit Saxena <sumit.saxena@broadcom.com>,
	linux-nvme@lists.infradead.org,
	Peter Rivera <peter.rivera@broadcom.com>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 13/14] megaraid_sas: NVME passthru command support
Date: Thu, 11 Jan 2018 10:46:20 -0700	[thread overview]
Message-ID: <20180111174619.GA2860@localhost.localdomain> (raw)
In-Reply-To: <e407e98c266c060412bfa8b64ded18df@mail.gmail.com>

On Wed, Jan 10, 2018 at 03:14:40PM -0700, Sathya Prakash Veerichetty wrote:
> In the case of RAID controllers, all of those drives and RAID volumes
> are exposed to the OS as generic SCSI devices

So even when used as a RAID member, there will be a device handle at
/dev/sdX for each NVMe device the megaraid controller manages?

  reply	other threads:[~2018-01-11 17:46 UTC|newest]

Thread overview: 32+ 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-05 13:35 ` Shivasharan S
2018-01-08 10:05 ` Christoph Hellwig
2018-01-08 10:05   ` Christoph Hellwig
2018-01-09 16:37   ` Kashyap Desai
2018-01-09 16:37     ` Kashyap Desai
2018-01-09 16:45     ` Christoph Hellwig
2018-01-09 16:45       ` Christoph Hellwig
2018-01-09 20:50       ` Douglas Gilbert
2018-01-09 20:50         ` Douglas Gilbert
2018-01-09 23:23         ` Keith Busch
2018-01-09 23:23           ` Keith Busch
2018-01-10  9:32           ` Kashyap Desai
2018-01-10  9:32             ` Kashyap Desai
2018-01-10 10:03         ` Kashyap Desai
2018-01-10 10:03           ` Kashyap Desai
2018-01-10 16:22     ` Bart Van Assche
2018-01-10 16:22       ` Bart Van Assche
2018-01-10 20:06       ` Douglas Gilbert
2018-01-10 20:06         ` Douglas Gilbert
2018-01-10 22:14         ` Sathya Prakash Veerichetty
2018-01-10 22:14           ` Sathya Prakash Veerichetty
2018-01-11 17:46           ` Keith Busch [this message]
2018-01-11 17:46             ` Keith Busch
2018-01-11 18:07             ` Sathya Prakash Veerichetty
2018-01-11 18:07               ` Sathya Prakash Veerichetty
2018-01-15 12:16               ` Kashyap Desai
2018-01-15 12:16                 ` Kashyap Desai
2018-01-16  3:06                 ` Martin K. Petersen
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=20180111174619.GA2860@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.