From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>, linux-sctp@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Neil Horman <nhorman@tuxdriver.com>
Subject: [PATCH net-next 0/2] sctp: add another two stream schedulers
Date: Tue, 7 Mar 2023 16:23:25 -0500 [thread overview]
Message-ID: <cover.1678224012.git.lucien.xin@gmail.com> (raw)
All SCTP stream schedulers are defined in rfc8260#section-3,
First-Come First-Served, Round-Robin and Priority-Based
Schedulers are already added in kernel.
This patchset adds another two schedulers: Fair Capacity
Scheduler and Weighted Fair Queueing Scheduler.
Note that the left one "Round-Robin Scheduler per Packet"
Scheduler is not implemented by this patch, as it's still
intrusive to be added in the current SCTP kernel code.
Xin Long (2):
sctp: add fair capacity stream scheduler
sctp: add weighted fair queueing stream scheduler
include/net/sctp/stream_sched.h | 2 +
include/net/sctp/structs.h | 8 ++
include/uapi/linux/sctp.h | 4 +-
net/sctp/Makefile | 3 +-
net/sctp/stream_sched.c | 2 +
net/sctp/stream_sched_fc.c | 225 ++++++++++++++++++++++++++++++++
6 files changed, 242 insertions(+), 2 deletions(-)
create mode 100644 net/sctp/stream_sched_fc.c
--
2.39.1
next reply other threads:[~2023-03-07 21:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 21:23 Xin Long [this message]
2023-03-07 21:23 ` [PATCH net-next 1/2] sctp: add fair capacity stream scheduler Xin Long
2023-03-07 21:48 ` Marcelo Ricardo Leitner
2023-03-09 10:31 ` Paolo Abeni
2023-03-10 0:38 ` Xin Long
2023-03-07 21:23 ` [PATCH net-next 2/2] sctp: add weighted fair queueing " Xin Long
2023-03-07 21:49 ` Marcelo Ricardo Leitner
2023-03-09 10:40 ` [PATCH net-next 0/2] sctp: add another two stream schedulers patchwork-bot+netdevbpf
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.1678224012.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=pabeni@redhat.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 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.