All of lore.kernel.org
 help / color / mirror / Atom feed
From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH 7/7 v2] nvme-fabrics: Add FC LLDD loopback driver to test FC-NVME
Date: Thu, 13 Oct 2016 02:53:22 -0700	[thread overview]
Message-ID: <20161013095322.GC16162@infradead.org> (raw)
In-Reply-To: <c438c009-48fa-5fe3-5dce-bdc105a9e489@broadcom.com>

On Wed, Oct 12, 2016@01:12:34PM -0700, James Smart wrote:
> You've lost me. The fc-nvme api on the initiator side has a sgl relative to
> the original io request, while the fc-nvmet api on the target side has a
> different sgl from the target fc-nvme transport to the LLDD for the range of
> data to exchange. They are sgl's as they expect to go to fc hw on each side.
> As they are independent sgl's on each side, we have to copy between them.

Oh, right - your target sgls aren't caller provided.  That's a little
sad when looking at this code, but if it doesn't affect real drivers
I guess it's fine in the end.

      reply	other threads:[~2016-10-13  9:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 23:09 [PATCH 7/7 v2] nvme-fabrics: Add FC LLDD loopback driver to test FC-NVME James Smart
2016-10-12 10:37 ` Christoph Hellwig
2016-10-12 20:12   ` James Smart
2016-10-13  9:53     ` Christoph Hellwig [this message]

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=20161013095322.GC16162@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 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.