public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jamal Hadi Salim <jhs@mojatatu•com>
To: Thomas Graf <tgraf@suug•ch>, Jiri Pirko <jiri@resnulli•us>
Cc: Hannes Frederic Sowa <hannes@stressinduktion•org>,
	netdev@vger•kernel.org, davem@davemloft•net, jesse@nicira•com
Subject: Re: [patch net-next] tc: introduce OpenFlow classifier
Date: Sun, 29 Mar 2015 20:45:02 -0400	[thread overview]
Message-ID: <55189C8E.7070705@mojatatu.com> (raw)
In-Reply-To: <20150327124938.GH12265@casper.infradead.org>

On 03/27/15 08:49, Thomas Graf wrote:

> So at that point you get fairly close to cls_flow in terms
> of functionality. Not sure why you want to keep them separate.
>

IMO, it is different enough to be separate.
Flow could do more of course (as could u32) but the lookup
approaches are different. And yes, ONF will probably make a press
release if you called it the openflow classifier (fingers crossed).

cheers,
jamal

  reply	other threads:[~2015-03-30  0:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 12:53 [patch net-next] tc: introduce OpenFlow classifier Jiri Pirko
2015-03-26 12:55 ` [patch iproute2/net-next] tc: add support for " Jiri Pirko
2015-03-26 13:25 ` [patch net-next] tc: introduce " Thomas Graf
2015-03-26 14:22   ` Jiri Pirko
2015-03-26 14:23 ` Hannes Frederic Sowa
2015-03-26 15:29   ` Jiri Pirko
2015-03-26 20:39     ` Hannes Frederic Sowa
2015-03-26 20:51       ` Daniel Borkmann
2015-03-27  6:07       ` Jiri Pirko
2015-03-27 11:44         ` Thomas Graf
2015-03-27 12:28           ` Jiri Pirko
2015-03-27 12:36             ` Thomas Graf
2015-03-27 12:45               ` Jiri Pirko
2015-03-27 12:49                 ` Thomas Graf
2015-03-30  0:45                   ` Jamal Hadi Salim [this message]
2015-03-30  0:39 ` Jamal Hadi Salim
2015-03-30  6:26   ` Jiri Pirko
2015-03-30 11:10     ` Jamal Hadi Salim
2015-03-30 12:18       ` 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=55189C8E.7070705@mojatatu.com \
    --to=jhs@mojatatu$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=hannes@stressinduktion$(echo .)org \
    --cc=jesse@nicira$(echo .)com \
    --cc=jiri@resnulli$(echo .)us \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=tgraf@suug$(echo .)ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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