From: Jiri Pirko <jiri@resnulli.us>
To: Jamal Hadi Salim <jhs@mojatatu.com>, f@nanopsycho
Cc: xiyou.wangcong@gmail.com, netdev@vger.kernel.org,
vladbu@nvidia.com, mleitner@redhat.com
Subject: Re: [PATCH RFC net-next 0/3] Introduce tc block ports tracking and use
Date: Wed, 16 Aug 2023 08:46:45 +0200 [thread overview]
Message-ID: <ZNxw1eHBdVeGCWH2@nanopsycho> (raw)
In-Reply-To: <20230815162530.150994-1-jhs@mojatatu.com>
Tue, Aug 15, 2023 at 06:25:27PM CEST, jhs@mojatatu.com wrote:
>In this patchset we introduce tc block netdev tracking infra.
>Patch 1 introduces the infra. Patch 2 exposes it to the datapath and patch 3
>shows its usage via a new tc action "blockcast".
This is very brief. Please describe motivation, how you solve the
problem, provide examples, etc. From the cover letter, the reader should
know what is going on without looking at the patches.
>
>
>Jamal Hadi Salim (3):
> Introduce tc block netdev tracking infra
> Expose tc block ports to the datapath
> Introduce blockcast tc action
>
> include/net/sch_generic.h | 8 +
> include/net/tc_wrapper.h | 5 +
> net/sched/Kconfig | 13 ++
> net/sched/Makefile | 1 +
> net/sched/act_blockcast.c | 315 ++++++++++++++++++++++++++++++++++++++
> net/sched/cls_api.c | 7 +-
> net/sched/sch_api.c | 83 +++++++++-
> net/sched/sch_generic.c | 37 ++++-
> 8 files changed, 463 insertions(+), 6 deletions(-)
> create mode 100644 net/sched/act_blockcast.c
>
>--
>2.34.1
>
prev parent reply other threads:[~2023-08-16 6:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 16:25 [PATCH RFC net-next 0/3] Introduce tc block ports tracking and use Jamal Hadi Salim
2023-08-15 16:25 ` [PATCH RFC net-next 1/3] Introduce tc block netdev tracking infra Jamal Hadi Salim
2023-08-15 16:25 ` [PATCH RFC net-next 2/3] Expose tc block ports to the datapath Jamal Hadi Salim
2023-08-15 17:52 ` Stephen Hemminger
2023-08-16 11:06 ` Jamal Hadi Salim
2023-08-16 12:58 ` Jamal Hadi Salim
2023-08-16 9:04 ` Simon Horman
2023-08-15 16:25 ` [PATCH RFC net-next 3/3] Introduce blockcast tc action Jamal Hadi Salim
2023-08-16 9:06 ` Simon Horman
2023-08-16 11:09 ` Jamal Hadi Salim
2023-08-16 6:46 ` Jiri Pirko [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=ZNxw1eHBdVeGCWH2@nanopsycho \
--to=jiri@resnulli.us \
--cc=f@nanopsycho \
--cc=jhs@mojatatu.com \
--cc=mleitner@redhat.com \
--cc=netdev@vger.kernel.org \
--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 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).