Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@infradead.org (Christoph Hellwig)
Subject: Question on NVMe SCSI Translation Ref 1.5
Date: Fri, 20 Nov 2015 10:32:06 -0800	[thread overview]
Message-ID: <20151120183206.GA11043@infradead.org> (raw)
In-Reply-To: <BL2PR04MB1634A1D6C773CDEC0C45D9A921A0@BL2PR04MB163.namprd04.prod.outlook.com>

Hi Jeffrey,

SG_IO is sent to a device node.  For actualy SCSI devices you'll
get the LUN from sdev->lun.  For NVMe there obviously aren't any LUNs,
so you'll have to come up with a tranlation.  The current Linux driver
translated namespaces 1 to LUN 0 and so on.  In general sending a
REPORT LUNS to a NVMe device node does not seem very useful, and I have
no idea why it even was specified.  Then again the whole SCSI
translation layer concept seems incredbile braindead and I think we
should at least optionally remove it from the NVMe driver.

  reply	other threads:[~2015-11-20 18:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 18:02 Question on NVMe SCSI Translation Ref 1.5 Jeffrey Lien
2015-11-20 18:32 ` Christoph Hellwig [this message]
2015-11-20 19:54   ` Robles, Raymond C
2015-11-21  8:18     ` 'Christoph Hellwig'

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=20151120183206.GA11043@infradead.org \
    --to=hch@infradead.org \
    /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