From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, marcelo.leitner@gmail.com,
nhorman@tuxdriver.com
Subject: Re: [PATCH net-next 0/2] sctp: add another two stream schedulers
Date: Thu, 09 Mar 2023 10:40:18 +0000 [thread overview]
Message-ID: <167835841852.16610.7402267659998000194.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1678224012.git.lucien.xin@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 7 Mar 2023 16:23:25 -0500 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [net-next,1/2] sctp: add fair capacity stream scheduler
https://git.kernel.org/netdev/net-next/c/4821a076eb60
- [net-next,2/2] sctp: add weighted fair queueing stream scheduler
https://git.kernel.org/netdev/net-next/c/42d452e7709f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-03-09 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 21:23 [PATCH net-next 0/2] sctp: add another two stream schedulers Xin Long
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 ` patchwork-bot+netdevbpf [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=167835841852.16610.7402267659998000194.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--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 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).