From: patchwork-bot+netdevbpf@kernel.org
To: Victor Nogueira <victor@mojatatu.com>
Cc: jhs@mojatatu.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, xiyou.wangcong@gmail.com,
jiri@resnulli.us, mleitner@redhat.com, vladbu@nvidia.com,
paulb@nvidia.com, pctammela@mojatatu.com, netdev@vger.kernel.org,
kernel@mojatatu.com
Subject: Re: [PATCH net-next v8 0/5] net/sched: Introduce tc block ports tracking and use
Date: Tue, 26 Dec 2023 21:30:24 +0000 [thread overview]
Message-ID: <170362622441.9388.9107098884966655363.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231219181623.3845083-1-victor@mojatatu.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 19 Dec 2023 15:16:18 -0300 you wrote:
> __context__
> The "tc block" is a collection of netdevs/ports which allow qdiscs to share
> match-action block instances (as opposed to the traditional tc filter per
> netdev/port)[1].
>
> Up to this point in the implementation, the block is unaware of its ports.
> This patch makes the tc block ports available to the datapath.
>
> [...]
Here is the summary with links:
- [net-next,v8,1/5] net/sched: Introduce tc block netdev tracking infra
https://git.kernel.org/netdev/net-next/c/913b47d3424e
- [net-next,v8,2/5] net/sched: cls_api: Expose tc block to the datapath
https://git.kernel.org/netdev/net-next/c/a7042cf8f231
- [net-next,v8,3/5] net/sched: act_mirred: Create function tcf_mirred_to_dev and improve readability
https://git.kernel.org/netdev/net-next/c/16085e48cb48
- [net-next,v8,4/5] net/sched: act_mirred: Add helper function tcf_mirred_replace_dev
https://git.kernel.org/netdev/net-next/c/415e38bf1d8d
- [net-next,v8,5/5] net/sched: act_mirred: Allow mirred to block
https://git.kernel.org/netdev/net-next/c/42f39036cda8
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-12-26 21:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 18:16 [PATCH net-next v8 0/5] net/sched: Introduce tc block ports tracking and use Victor Nogueira
2023-12-19 18:16 ` [PATCH net-next v8 1/5] net/sched: Introduce tc block netdev tracking infra Victor Nogueira
2023-12-28 11:40 ` Ido Schimmel
2023-12-28 11:50 ` Ido Schimmel
2023-12-28 12:35 ` Jamal Hadi Salim
2023-12-28 14:13 ` Victor Nogueira
2023-12-19 18:16 ` [PATCH net-next v8 2/5] net/sched: cls_api: Expose tc block to the datapath Victor Nogueira
2023-12-19 18:16 ` [PATCH net-next v8 3/5] net/sched: act_mirred: Create function tcf_mirred_to_dev and improve readability Victor Nogueira
2023-12-19 18:16 ` [PATCH net-next v8 4/5] net/sched: act_mirred: Add helper function tcf_mirred_replace_dev Victor Nogueira
2023-12-19 18:16 ` [PATCH net-next v8 5/5] net/sched: act_mirred: Allow mirred to block Victor Nogueira
2023-12-26 21:30 ` 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=170362622441.9388.9107098884966655363.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kernel@mojatatu.com \
--cc=kuba@kernel.org \
--cc=mleitner@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulb@nvidia.com \
--cc=pctammela@mojatatu.com \
--cc=victor@mojatatu.com \
--cc=vladbu@nvidia.com \
--cc=xiyou.wangcong@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 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.