From: Helen Koike <helen.koike@collabora.co.uk>
To: hch@infradead.org, mlin@kernel.org, fes@google.com,
keith.busch@intel.com, rlnelson@google.com, axboe@fb.com,
digitaleric@google.com, tytso@mit.edu, mikew@google.com,
monish@google.com
Cc: Helen Koike <helen.koike@collabora.co.uk>,
linux-kernel@vger.kernel.org (open list),
linux-nvme@lists.infradead.org (open list:NVM EXPRESS DRIVER),
linux-pci@vger.kernel.org (open list:PCI SUBSYSTEM)
Subject: [PATCH v3 RFC 0/2] Virtual NVMe device optimization
Date: Mon, 15 Aug 2016 22:41:18 -0300 [thread overview]
Message-ID: <cover.1471308889.git.helen.koike@collabora.co.uk> (raw)
In-Reply-To: <1460657059-21214-1-git-send-email-helen.koike@collabora.co.uk>
Please, check commit "nvme: improve performance for virtual NVMe devices" for more details
Commit "PCI: Add Google device ID" only adds a new id in pci_ids.h
Patches are based in the linux-block/for-next branch and available here:
https://github.com/helen-fornazier/opw-staging/commits/nvme/dev
Helen Koike (1):
PCI: Add Google device ID
Rob Nelson (1):
nvme: improve performance for virtual NVMe devices
drivers/nvme/host/Kconfig | 11 ++++
drivers/nvme/host/Makefile | 1 +
drivers/nvme/host/pci.c | 29 ++++++++++-
drivers/nvme/host/vdb.c | 125 +++++++++++++++++++++++++++++++++++++++++++++
drivers/nvme/host/vdb.h | 118 ++++++++++++++++++++++++++++++++++++++++++
include/linux/nvme.h | 17 ++++++
include/linux/pci_ids.h | 2 +
7 files changed, 301 insertions(+), 2 deletions(-)
create mode 100644 drivers/nvme/host/vdb.c
create mode 100644 drivers/nvme/host/vdb.h
--
1.9.1
next parent reply other threads:[~2016-08-16 1:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1460657059-21214-1-git-send-email-helen.koike@collabora.co.uk>
2016-08-16 1:41 ` Helen Koike [this message]
2016-08-16 1:41 ` [PATCH v3 RFC 1/2] PCI: Add Google device ID Helen Koike
2016-08-18 21:59 ` Bjorn Helgaas
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=cover.1471308889.git.helen.koike@collabora.co.uk \
--to=helen.koike@collabora.co.uk \
--cc=axboe@fb.com \
--cc=digitaleric@google.com \
--cc=fes@google.com \
--cc=hch@infradead.org \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=mikew@google.com \
--cc=mlin@kernel.org \
--cc=monish@google.com \
--cc=rlnelson@google.com \
--cc=tytso@mit.edu \
/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).