From: scott.bauer@intel.com (Scott Bauer)
Subject: [RFC PATCH 0/2] Re-work CMB and add WDS support.
Date: Thu, 19 Jul 2018 17:06:26 -0600 [thread overview]
Message-ID: <20180719230628.31494-1-scott.bauer@intel.com> (raw)
The first patch adds CMB into a generic pool, from there we'll allocate
from the pool for the submission queues. In the future we can allocate SGLs
and PRPs from the pool as well.
The second patch unfortunately bounces (memcpys) the data from host to CMB.
I originally tried to map the CMB into userspace via a custom nvme mmap
handler, but I'm dumb and could never get gup for direct io working correctly.
next reply other threads:[~2018-07-19 23:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 23:06 Scott Bauer [this message]
2018-07-19 23:06 ` [RCF PATCH 1/2] nvme: pci: Move CMB allocation into a pool Scott Bauer
2018-07-20 14:49 ` Christoph Hellwig
2018-07-19 23:06 ` [RCF PATCH 2/2] nvme-pci: Bounce data from Host memory to CMB Memory Scott Bauer
2018-07-20 14:23 ` Keith Busch
2018-07-20 14:49 ` Christoph Hellwig
2018-07-20 14:53 ` Scott Bauer
2018-07-20 14:46 ` [RFC PATCH 0/2] Re-work CMB and add WDS support Christoph Hellwig
2018-07-20 14:50 ` Scott Bauer
2018-07-20 16:01 ` 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=20180719230628.31494-1-scott.bauer@intel.com \
--to=scott.bauer@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 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).