netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: David Miller <davem@davemloft.net>,
	Daniel Borkmann <daniel@iogearbox.net>,
	nikolay@cumulusnetworks.com,
	Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [RFC PATCH net-next 1/1] Introduce skbmod action
Date: Tue, 12 Jul 2016 10:10:15 -0700	[thread overview]
Message-ID: <CAM_iQpWNxZjWM-f_siOuXf+w_mgxKay9S8kAmUTD+8YLXp2S+g@mail.gmail.com> (raw)
In-Reply-To: <1468239164-17898-1-git-send-email-jhs@emojatatu.com>

On Mon, Jul 11, 2016 at 5:12 AM, Jamal Hadi Salim <jhs@mojatatu.com> wrote:
> From: Jamal Hadi Salim <jhs@mojatatu.com>
>
> This action is intended to be an upgrade from a usability perspective
> from pedit. Compare this:
>

Definitely agree we need a more user-friendly interface.

>
> pedit is a good starting point - but once you start going to a large
> number of policies then from a programmability, ops and usability point
> of view you need something with more succint params.
>

But it is still unclear why we can't just build something on top of
pedit? Since pedit accepts keys like u32, user-space is free to
introduce any wrapper on top of it.

It should not be a problem for libnl3 to build anything on top too.

  reply	other threads:[~2016-07-12 17:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11 12:12 [RFC PATCH net-next 1/1] Introduce skbmod action Jamal Hadi Salim
2016-07-12 17:10 ` Cong Wang [this message]
2016-07-16 14:28   ` Jamal Hadi Salim
2016-07-17 16:32     ` Cong Wang

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_iQpWNxZjWM-f_siOuXf+w_mgxKay9S8kAmUTD+8YLXp2S+g@mail.gmail.com \
    --to=xiyou.wangcong@gmail.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=jhs@mojatatu.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.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).