From: scott.bauer@intel.com (Scott Bauer)
Subject: [RCF PATCH 2/2] nvme-pci: Bounce data from Host memory to CMB Memory
Date: Fri, 20 Jul 2018 08:53:02 -0600 [thread overview]
Message-ID: <20180720145301.GC9294@sbauer-Z170X-UD5> (raw)
In-Reply-To: <20180720144949.GC29886@infradead.org>
On Fri, Jul 20, 2018@07:49:49AM -0700, Christoph Hellwig wrote:
> On Fri, Jul 20, 2018@08:23:43AM -0600, Keith Busch wrote:
> > On Thu, Jul 19, 2018@05:06:28PM -0600, Scott Bauer wrote:
> > > Signed-off-by: Scott Bauer <scott.bauer at intel.com>
> >
> > What does this gain us? I don't think this would do anything except
> > increase the CPU utilization. If this actually buys additional
> > performance, could you include some relative data and workload
> > characteristics in the changelog?
>
> Yes, as-is this seems rather counter productive..
Unfortunately I still don't have a drive to do perf testing on. The
only thing I can do is quickly hack this into QEMU, but I suspect that's
far too different to get us any relevant numbers.
next prev parent reply other threads:[~2018-07-20 14:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 23:06 [RFC PATCH 0/2] Re-work CMB and add WDS support Scott Bauer
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 [this message]
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=20180720145301.GC9294@sbauer-Z170X-UD5 \
--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