From: israelr@mellanox.com (Israel Rukshin)
Subject: [PATCH 0/5 V2] nvme: Add type of service (TOS) configuration
Date: Tue, 13 Aug 2019 16:17:25 +0300 [thread overview]
Message-ID: <1565702251-17198-1-git-send-email-israelr@mellanox.com> (raw)
Hi All,
This series adds TOS configuration for TCP and RDMA transports.
It provides clients the ability to segregate traffic flows for different
type of data.
One of the TOS usage is bandwidth management which allows setting bandwidth
limits for QoS classes, e.g. 80% bandwidth to controllers at QoS class A
and 20% to controllers at QoS class B.
Changes from v1:
- Add TCP TOS configuration
Israel Rukshin (5):
nvme-fabrics: Add type of service (TOS) configuration
nvme-rdma: Add TOS for rdma transport
nvme-tcp: Use struct nvme_ctrl directly
nvme-tcp: Add TOS for tcp transport
nvmet-tcp: Add TOS for tcp transport
drivers/nvme/host/fabrics.c | 16 +++++++++++++++-
drivers/nvme/host/fabrics.h | 3 +++
drivers/nvme/host/rdma.c | 6 ++++--
drivers/nvme/host/tcp.c | 32 ++++++++++++++++++++++----------
drivers/nvme/target/tcp.c | 11 +++++++++++
5 files changed, 55 insertions(+), 13 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-08-13 13:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 13:17 Israel Rukshin [this message]
2019-08-13 13:17 ` [PATCH] nvme-cli/fabrics: Add tos param to connect cmd Israel Rukshin
2019-08-13 16:43 ` Sagi Grimberg
2019-08-14 7:42 ` Israel Rukshin
2019-08-13 13:17 ` [PATCH 1/5] nvme-fabrics: Add type of service (TOS) configuration Israel Rukshin
2019-08-13 16:40 ` Sagi Grimberg
2019-08-13 17:55 ` James Smart
2019-08-13 13:17 ` [PATCH 2/5] nvme-rdma: Add TOS for rdma transport Israel Rukshin
2019-08-13 16:40 ` Sagi Grimberg
2019-08-13 13:17 ` [PATCH 3/5] nvme-tcp: Use struct nvme_ctrl directly Israel Rukshin
2019-08-13 16:41 ` Sagi Grimberg
2019-08-13 13:17 ` [PATCH 4/5] nvme-tcp: Add TOS for tcp transport Israel Rukshin
2019-08-13 16:41 ` Sagi Grimberg
2019-08-13 13:17 ` [PATCH 5/5] nvmet-tcp: " Israel Rukshin
2019-08-13 16:41 ` Sagi Grimberg
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=1565702251-17198-1-git-send-email-israelr@mellanox.com \
--to=israelr@mellanox.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;
as well as URLs for NNTP newsgroup(s).