From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH v3 0/5] implement nvmf read/write queue maps
Date: Thu, 13 Dec 2018 09:59:30 +0100 [thread overview]
Message-ID: <20181213085930.GA1840@lst.de> (raw)
In-Reply-To: <20181212073858.7102-1-sagi@grimberg.me>
Thanks,
applied to nvme-4.21.
prev parent reply other threads:[~2018-12-13 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 7:38 [PATCH v3 0/5] implement nvmf read/write queue maps Sagi Grimberg
2018-12-12 7:38 ` [PATCH v3 1/5] blk-mq-rdma: pass in queue map to blk_mq_rdma_map_queues Sagi Grimberg
2018-12-12 7:38 ` [PATCH v3 2/5] nvme-fabrics: add missing nvmf_ctrl_options documentation Sagi Grimberg
2018-12-12 7:38 ` [PATCH v3 3/5] nvme-fabrics: allow user to set nr_write_queues for separate queue maps Sagi Grimberg
2018-12-12 7:38 ` [PATCH v3 4/5] nvme-tcp: support separate queue maps for read and write Sagi Grimberg
2018-12-12 7:38 ` [PATCH v3 5/5] nvme-rdma: " Sagi Grimberg
2018-12-13 8:59 ` 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=20181213085930.GA1840@lst.de \
--to=hch@lst.de \
/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).