From: patchwork-bot+netdevbpf@kernel.org
To: Peilin Ye <yepeilin.cs@gmail.com>
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, cong.wang@bytedance.com,
peilin.ye@bytedance.com
Subject: Re: [PATCH RESEND net-next 1/2] net/sched: act_skbmod: Add SKBMOD_F_ECN option support
Date: Wed, 28 Jul 2021 12:40:05 +0000 [thread overview]
Message-ID: <162747600550.31652.10734754907124081471.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <f5bd3c60662ec0982cccd8951990796b87d1f985.1627434177.git.peilin.ye@bytedance.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Tue, 27 Jul 2021 18:33:15 -0700 you wrote:
> From: Peilin Ye <peilin.ye@bytedance.com>
>
> Currently, when doing rate limiting using the tc-police(8) action, the
> easiest way is to simply drop the packets which exceed or conform the
> configured bandwidth limit. Add a new option to tc-skbmod(8), so that
> users may use the ECN [1] extension to explicitly inform the receiver
> about the congestion instead of dropping packets "on the floor".
>
> [...]
Here is the summary with links:
- [RESEND,net-next,1/2] net/sched: act_skbmod: Add SKBMOD_F_ECN option support
https://git.kernel.org/netdev/net-next/c/56af5e749f20
- [RESEND,net-next,2/2] tc-testing: Add control-plane selftest for skbmod SKBMOD_F_ECN option
https://git.kernel.org/netdev/net-next/c/68f9884837c6
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:[~2021-07-28 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 1:33 [PATCH RESEND net-next 1/2] net/sched: act_skbmod: Add SKBMOD_F_ECN option support Peilin Ye
2021-07-28 1:33 ` [PATCH RESEND net-next 2/2] tc-testing: Add control-plane selftest for skbmod SKBMOD_F_ECN option Peilin Ye
2021-07-28 12: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=162747600550.31652.10734754907124081471.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cong.wang@bytedance.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peilin.ye@bytedance.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yepeilin.cs@gmail.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).