[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220304092754.2721-1-sunmingbao@tom.com>
Date: Fri, 4 Mar 2022 17:27:52 +0800
From: Mingbao Sun <sunmingbao@....com>
To: Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...com>,
Christoph Hellwig <hch@....de>,
Sagi Grimberg <sagi@...mberg.me>,
Chaitanya Kulkarni <kch@...dia.com>,
linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Cc: sunmingbao@....com, tyler.sun@...l.com, ping.gan@...l.com,
yanxiu.cai@...l.com, libin.zhang@...l.com, ao.sun@...l.com
Subject: [PATCH 0/2] NVMe_over_TCP: support specifying the congestion-control
From: Mingbao Sun <tyler.sun@...l.com>
Hi all,
congestion-control could have a noticeable impaction on the
performance of TCP-based communications. This is of course true
to NVMe_over_TCP.
Different congestion-controls (e.g., cubic, dctcp) are suitable for
different scenarios. Proper adoption of congestion control would benefit
the performance. On the contrary, the performance could be destroyed.
Though we can specify the congestion-control of NVMe_over_TCP via
writing '/proc/sys/net/ipv4/tcp_congestion_control', but this also
changes the congestion-control of all the future TCP sockets that
have not been explicitly assigned the congestion-control, thus bringing
potential impaction on their performance.
So it makes sense to make NVMe_over_TCP support specifying the
congestion-control.
The first commit addresses the target side, and the second one
addresses the host side.
Mingbao Sun (2):
nvmet-tcp: support specifying the congestion-control
nvme-tcp: support specifying the congestion-control
drivers/nvme/host/fabrics.c | 24 ++++++++++++++++
drivers/nvme/host/fabrics.h | 2 ++
drivers/nvme/host/tcp.c | 20 ++++++++++++-
drivers/nvme/target/configfs.c | 52 ++++++++++++++++++++++++++++++++++
drivers/nvme/target/nvmet.h | 1 +
drivers/nvme/target/tcp.c | 27 ++++++++++++++++++
6 files changed, 125 insertions(+), 1 deletion(-)
--
2.26.2
Powered by blists - more mailing lists