linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme: support bi-directional commands
Date: Wed, 7 Dec 2016 18:59:59 +0100	[thread overview]
Message-ID: <20161207175959.GA25611@lst.de> (raw)
In-Reply-To: <20161207180723.GE29574@localhost.localdomain>

On Wed, Dec 07, 2016@01:07:24PM -0500, Keith Busch wrote:
> On Wed, Dec 07, 2016@06:44:27PM +0100, Christoph Hellwig wrote:
> > On Wed, Dec 07, 2016@12:50:50PM -0500, Keith Busch wrote:
> > > NVMe defines this capability, so why would we want to make it unreachable
> > > in Linux?
> > 
> > NVMe defines no user of it, so that defintion is entirely theoretical
> > and it's a giant mess
> 
> It defines the use, but no user today. We can burn that bridge when we
> get there.

It does not define anything related to bidi comments.  The only mention
of bidirection is in the explanation of the table column.  And I'm not
being mean here - your patch assumes bidi commands would use the
a single data pointer for in and out data.  On the other hand all
bidirectional commands in SCSI do use separate data in and data out
buffers.  So any command "ported" from SCSI would work completely
differently from whatever vendor specific command you're trying to
support.

Please go to the NVMe committee first and define semantics for
bidirectional commands first.  After that we can decide how to support
them in Linux.

  reply	other threads:[~2016-12-07 17:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07 17:39 [PATCH] nvme: support bi-directional commands Keith Busch
2016-12-07 17:33 ` Christoph Hellwig
2016-12-07 17:50   ` Keith Busch
2016-12-07 17:44     ` Christoph Hellwig
2016-12-07 18:07       ` Keith Busch
2016-12-07 17:59         ` Christoph Hellwig [this message]
2016-12-07 18:15           ` 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=20161207175959.GA25611@lst.de \
    --to=hch@lst.de \
    /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).