From: Thomas Graf <tgraf@suug.ch>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Hannes Frederic Sowa <hannes@stressinduktion.org>,
netdev@vger.kernel.org, davem@davemloft.net, jhs@mojatatu.com,
jesse@nicira.com
Subject: Re: [patch net-next] tc: introduce OpenFlow classifier
Date: Fri, 27 Mar 2015 12:49:38 +0000 [thread overview]
Message-ID: <20150327124938.GH12265@casper.infradead.org> (raw)
In-Reply-To: <20150327124513.GB2172@nanopsycho.orion>
On 03/27/15 at 01:45pm, Jiri Pirko wrote:
> Fri, Mar 27, 2015 at 01:36:27PM CET, tgraf@suug.ch wrote:
> >You'll probably end up with a hash as well. I doubt that you
> >want to walk through a linear list of matches in the long term.
> >Not sure about your plans though.
>
> Sure, that was supposed next step, to change this to hash list.
So at that point you get fairly close to cls_flow in terms
of functionality. Not sure why you want to keep them separate.
next prev parent reply other threads:[~2015-03-27 12:49 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 [this message]
2015-03-30 0:45 ` Jamal Hadi Salim
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=20150327124938.GH12265@casper.infradead.org \
--to=tgraf@suug.ch \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=jesse@nicira.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.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 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).