From: Sagi Grimberg <sagi@grimberg.me> To: linux-nvme@lists.infradead.org Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <keith.busch@intel.com>, linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk> Subject: [PATCH 0/5] implement nvmf read/write queue maps Date: Tue, 11 Dec 2018 02:49:30 -0800 [thread overview] Message-ID: <20181211104936.25333-1-sagi@grimberg.me> (raw) This set implements read/write queue maps to nvmf (implemented in tcp and rdma). We basically allow the users to pass in nr_write_queues argument that will basically maps a separate set of queues to host write I/O (or more correctly non-read I/O) and a set of queues to hold read I/O (which is now controlled by the known nr_io_queues). A patchset that restores nvme-rdma polling is in the pipe. The polling is less trivial because: 1. we can find non I/O completions in the cq (i.e. memreg) 2. we need to start with non-polling for a sane connect and then switch to polling which is not trivial behind the cq API we use. Note that read/write separation for rdma but especially tcp this can be very clear win as we minimize the risk for head-of-queue blocking for mixed workloads over a single tcp byte stream. Sagi Grimberg (5): blk-mq-rdma: pass in queue map to blk_mq_rdma_map_queues nvme-fabrics: add missing nvmf_ctrl_options documentation nvme-fabrics: allow user to set nr_write_queues for separate queue maps nvme-tcp: support separate queue maps for read and write nvme-rdma: support read/write queue separation block/blk-mq-rdma.c | 8 +++--- drivers/nvme/host/fabrics.c | 15 ++++++++++- drivers/nvme/host/fabrics.h | 6 +++++ drivers/nvme/host/rdma.c | 39 ++++++++++++++++++++++++--- drivers/nvme/host/tcp.c | 53 ++++++++++++++++++++++++++++++++----- include/linux/blk-mq-rdma.h | 2 +- 6 files changed, 108 insertions(+), 15 deletions(-) -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: sagi@grimberg.me (Sagi Grimberg) Subject: [PATCH 0/5] implement nvmf read/write queue maps Date: Tue, 11 Dec 2018 02:49:30 -0800 [thread overview] Message-ID: <20181211104936.25333-1-sagi@grimberg.me> (raw) This set implements read/write queue maps to nvmf (implemented in tcp and rdma). We basically allow the users to pass in nr_write_queues argument that will basically maps a separate set of queues to host write I/O (or more correctly non-read I/O) and a set of queues to hold read I/O (which is now controlled by the known nr_io_queues). A patchset that restores nvme-rdma polling is in the pipe. The polling is less trivial because: 1. we can find non I/O completions in the cq (i.e. memreg) 2. we need to start with non-polling for a sane connect and then switch to polling which is not trivial behind the cq API we use. Note that read/write separation for rdma but especially tcp this can be very clear win as we minimize the risk for head-of-queue blocking for mixed workloads over a single tcp byte stream. Sagi Grimberg (5): blk-mq-rdma: pass in queue map to blk_mq_rdma_map_queues nvme-fabrics: add missing nvmf_ctrl_options documentation nvme-fabrics: allow user to set nr_write_queues for separate queue maps nvme-tcp: support separate queue maps for read and write nvme-rdma: support read/write queue separation block/blk-mq-rdma.c | 8 +++--- drivers/nvme/host/fabrics.c | 15 ++++++++++- drivers/nvme/host/fabrics.h | 6 +++++ drivers/nvme/host/rdma.c | 39 ++++++++++++++++++++++++--- drivers/nvme/host/tcp.c | 53 ++++++++++++++++++++++++++++++++----- include/linux/blk-mq-rdma.h | 2 +- 6 files changed, 108 insertions(+), 15 deletions(-) -- 2.17.1
next reply other threads:[~2018-12-11 10:50 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-12-11 10:49 Sagi Grimberg [this message] 2018-12-11 10:49 ` [PATCH 0/5] implement nvmf read/write queue maps Sagi Grimberg 2018-12-11 10:49 ` [PATCH 1/5] blk-mq-rdma: pass in queue map to blk_mq_rdma_map_queues Sagi Grimberg 2018-12-11 10:49 ` Sagi Grimberg 2018-12-11 13:34 ` Christoph Hellwig 2018-12-11 13:34 ` Christoph Hellwig 2018-12-11 10:49 ` [PATCH 2/5] nvme-fabrics: add missing nvmf_ctrl_options documentation Sagi Grimberg 2018-12-11 10:49 ` Sagi Grimberg 2018-12-11 13:35 ` Christoph Hellwig 2018-12-11 13:35 ` Christoph Hellwig 2018-12-11 10:49 ` [PATCH 3/5] nvme-fabrics: allow user to set nr_write_queues for separate queue maps Sagi Grimberg 2018-12-11 10:49 ` Sagi Grimberg 2018-12-11 13:35 ` Christoph Hellwig 2018-12-11 13:35 ` Christoph Hellwig 2018-12-11 10:49 ` [PATCH 4/5] nvme-tcp: support separate queue maps for read and write Sagi Grimberg 2018-12-11 10:49 ` Sagi Grimberg 2018-12-11 13:41 ` Christoph Hellwig 2018-12-11 13:41 ` Christoph Hellwig 2018-12-11 23:11 ` Sagi Grimberg 2018-12-11 23:11 ` Sagi Grimberg 2018-12-11 10:49 ` [PATCH 5/5] nvme-rdma: support read/write queue separation Sagi Grimberg 2018-12-11 10:49 ` Sagi Grimberg 2018-12-11 13:42 ` Christoph Hellwig 2018-12-11 13:42 ` Christoph Hellwig 2018-12-11 10:49 ` [PATCH nvme-cli 6/5] fabrics: pass in nr_write_queues Sagi Grimberg 2018-12-11 10:49 ` Sagi Grimberg 2018-12-11 19:30 ` Keith Busch 2018-12-11 19:30 ` Keith Busch 2018-12-11 23:34 ` Sagi Grimberg 2018-12-11 23:34 ` Sagi Grimberg 2018-12-11 13:28 ` [PATCH 0/5] implement nvmf read/write queue maps Christoph Hellwig 2018-12-11 13:28 ` 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=20181211104936.25333-1-sagi@grimberg.me \ --to=sagi@grimberg.me \ --cc=axboe@kernel.dk \ --cc=hch@lst.de \ --cc=keith.busch@intel.com \ --cc=linux-block@vger.kernel.org \ --cc=linux-nvme@lists.infradead.org \ /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: linkBe 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.