All of lore.kernel.org
 help / color / mirror / Atom feed
From: martin.petersen@oracle.com (Martin K. Petersen)
Subject: [RFC PATCH] nvme-pci: Bounce buffer for interleaved metadata
Date: Tue, 27 Feb 2018 22:46:32 -0500	[thread overview]
Message-ID: <yq1371l4vzb.fsf@oracle.com> (raw)
In-Reply-To: <5662c6d9-0c87-6074-12b8-39db53ce3c7f@grimberg.me> (Sagi Grimberg's message of "Sun, 25 Feb 2018 19:30:48 +0200")


Sagi,

> It makes sense for FC (and few RDMA devices) that already get
> interleaved metadata from the wire to keep it as is instead of
> scattering it if the backend nvme device supports interleaved mode...

Yeah, assuming that the PI doesn't have to get translated.

> I would say that this support for this is something that belongs in
> the block layer. IIRC mkp also expressed interest in using
> preadv2/pwritev2 to for user-space to use DIF with some accounting on
> the iovec

Indeed.

> so maybe we can add a flag for interleaved metadata.

What would the use case be for this? Userspace target driver? I know
lots of widgets that rely on interleaved but they are all using SPDK.

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2018-02-28  3:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-24  0:05 [RFC PATCH] nvme-pci: Bounce buffer for interleaved metadata Keith Busch
2018-02-25 17:30 ` Sagi Grimberg
2018-02-26 16:49   ` Keith Busch
2018-02-28  3:46   ` Martin K. Petersen [this message]
2018-03-01  9:22     ` Sagi Grimberg
2018-02-28  3:42 ` Martin K. Petersen
2018-02-28 16:35   ` Keith Busch
2018-02-28 16:37     ` Christoph Hellwig
2018-02-28 19:54       ` 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=yq1371l4vzb.fsf@oracle.com \
    --to=martin.petersen@oracle.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.