netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: Felipe Magno de Almeida <felipe@sipanda.io>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
	Jiri Pirko <jiri@resnulli.us>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>,
	boris.sukholitko@broadcom.com, vadym.kochan@plvision.eu,
	ilya.lifshits@broadcom.com, Vlad Buslov <vladbu@nvidia.com>,
	Ido Schimmel <idosch@idosch.org>,
	paulb@nvidia.com, Davide Caratti <dcaratti@redhat.com>,
	Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
	Amritha Nambiar <amritha.nambiar@intel.com>,
	"Samudrala, Sridhar" <sridhar.samudrala@intel.com>,
	tom Herbert <tom@sipanda.io>,
	Pedro Tammela <pctammela@mojatatu.com>,
	Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH RFC net-next 0/2] net:sched: Introduce tc flower2 classifier based on PANDA parser in kernel
Date: Tue, 21 Sep 2021 21:38:20 -0700	[thread overview]
Message-ID: <CAM_iQpUkdz_EjiuPRF_qKBp_ZHok_c8+pr4skCWGs_QTeLWpwA@mail.gmail.com> (raw)
In-Reply-To: <20210916200041.810-1-felipe@expertise.dev>

On Thu, Sep 16, 2021 at 1:02 PM Felipe Magno de Almeida
<felipe@sipanda.io> wrote:
>
> The PANDA parser, introduced in [1], addresses most of these problems
> and introduces a developer friendly highly maintainable approach to
> adding extensions to the parser. This RFC patch takes a known consumer
> of flow dissector - tc flower - and  shows how it could make use of
> the PANDA Parser by mostly cutnpaste of the flower code. The new
> classifier is called "flower2". The control semantics of flower are
> maintained but the flow dissector parser is replaced with a PANDA
> Parser. The iproute2 patch is sent separately - but you'll notice
> other than replacing the user space tc commands with "flower2"  the
> syntax is exactly the same. To illustrate the flexibility of PANDA we
> show a simple use case of the issues described in [2] when flower
> consumes PANDA. The PANDA Parser is part of the PANDA programming
> model for network datapaths, this is described in
> https://github.com/panda-net/panda.

My only concern is that is there any way to reuse flower code instead
of duplicating most of them? Especially when you specifically mentioned
flower2 has the same user-space syntax as flower, this makes code
reusing more reasonable.

Thanks.

  parent reply	other threads:[~2021-09-22  4:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16 20:00 [PATCH RFC net-next 0/2] net:sched: Introduce tc flower2 classifier based on PANDA parser in kernel Felipe Magno de Almeida
2021-09-16 20:00 ` [PATCH RFC net-next 1/2] net: Add PANDA network packet parser Felipe Magno de Almeida
2021-09-16 20:00 ` [PATCH RFC net-next 2/2] net/sched: Add flower2 packet classifier based on flower and PANDA parser Felipe Magno de Almeida
2021-09-22 20:33   ` Marcelo Ricardo Leitner
2021-09-23 13:33     ` Felipe Magno de Almeida
2021-09-22  4:38 ` Cong Wang [this message]
2021-09-22  4:46   ` [PATCH RFC net-next 0/2] net:sched: Introduce tc flower2 classifier based on PANDA parser in kernel Jiri Pirko
2021-09-22 14:42     ` Tom Herbert
2021-09-22 15:49       ` Simon Horman
2021-09-22 17:28         ` Tom Herbert
2021-09-22 18:00           ` Simon Horman
2021-09-22 21:06             ` Tom Herbert
2021-09-22 21:40               ` John Fastabend
2021-09-22 23:51                 ` Tom Herbert
2021-09-23  1:28                   ` John Fastabend
     [not found]                     ` <CAOuuhY-ujF_EPm6qeHAfgs6O0_-yyfZLMryYx4pS=Yd1XLor+A@mail.gmail.com>
2021-09-23  3:25                       ` John Fastabend
2021-09-23  4:34                         ` Tom Herbert
2021-09-23 13:26                         ` Jamal Hadi Salim
2021-09-24  3:55                           ` John Fastabend
2021-09-24 16:21                             ` Tom Herbert
2021-09-24 19:14                               ` John Fastabend
2021-09-26 15:54                             ` Jamal Hadi Salim
2021-09-22 20:25           ` Marcelo Ricardo Leitner
2021-09-22 23:04             ` Tom Herbert

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=CAM_iQpUkdz_EjiuPRF_qKBp_ZHok_c8+pr4skCWGs_QTeLWpwA@mail.gmail.com \
    --to=xiyou.wangcong@gmail.com \
    --cc=amritha.nambiar@intel.com \
    --cc=boris.sukholitko@broadcom.com \
    --cc=dcaratti@redhat.com \
    --cc=eric.dumazet@gmail.com \
    --cc=felipe@sipanda.io \
    --cc=idosch@idosch.org \
    --cc=ilya.lifshits@broadcom.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=paulb@nvidia.com \
    --cc=pctammela@mojatatu.com \
    --cc=sridhar.samudrala@intel.com \
    --cc=tom@sipanda.io \
    --cc=vadym.kochan@plvision.eu \
    --cc=vladbu@nvidia.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).