All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cong Wang <cwang@twopensource.com>
To: Daniel Borkmann <dborkman@redhat.com>
Cc: Jiri Pirko <jiri@resnulli.us>, netdev <netdev@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	Jamal Hadi Salim <jhs@mojatatu.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Alexei Starovoitov <ast@plumgrid.com>
Subject: Re: [patch net-next] tc: add BPF based action
Date: Wed, 7 Jan 2015 10:46:35 -0800	[thread overview]
Message-ID: <CAHA+R7PJNFfekrLx6j+c+C4zsgVk1r5jm-hXv5=f4hLkq932pA@mail.gmail.com> (raw)
In-Reply-To: <54AD7C03.3010904@redhat.com>

On Wed, Jan 7, 2015 at 10:33 AM, Daniel Borkmann <dborkman@redhat.com> wrote:
> On 01/07/2015 05:43 PM, Jiri Pirko wrote:
>>
>> This action provides a possibility to exec custom BPF code.
>
>
> Can you elaborate a bit more on the particular use-case, and
> what scenarios are unsolveable with the BPF filter we already
> have in tc? Just wondering, since you're using BPF for the
> purpose of classifying (but just from the context of actions)
> what about a possibility of a generic container for reusing
> (any) classifier from the framework, so we would not need to
> duplicate code?
>

+1

Also as its name tells, BPF is a filter, why it could be used
as an action here? (I don't follow eBPF though.)

  reply	other threads:[~2015-01-07 18:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07 16:43 [patch net-next] tc: add BPF based action Jiri Pirko
2015-01-07 16:47 ` [patch iproute2 1/2] tc: push bpf common code into separate file Jiri Pirko
2015-01-07 16:47   ` [patch iproute2 2/2] tc: add support for BPF based actions Jiri Pirko
2015-01-07 18:50     ` Cong Wang
2015-01-07 19:52       ` Jiri Pirko
2015-01-07 19:58         ` Cong Wang
2015-01-14  1:19     ` Stephen Hemminger
2015-01-14  9:19       ` Jiri Pirko
2015-01-07 18:33 ` [patch net-next] tc: add BPF based action Daniel Borkmann
2015-01-07 18:46   ` Cong Wang [this message]
2015-01-08  7:26   ` Jiri Pirko
2015-01-08 14:55 ` Hannes Frederic Sowa
2015-01-08 15:01   ` Jiri Pirko
2015-01-08 19:04 Alexei Starovoitov
2015-01-12 10:52 ` Jiri Pirko

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='CAHA+R7PJNFfekrLx6j+c+C4zsgVk1r5jm-hXv5=f4hLkq932pA@mail.gmail.com' \
    --to=cwang@twopensource.com \
    --cc=ast@plumgrid.com \
    --cc=davem@davemloft.net \
    --cc=dborkman@redhat.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    /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.