[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54C3986A.9070105@mojatatu.com>
Date: Sat, 24 Jan 2015 08:04:42 -0500
From: Jamal Hadi Salim <jhs@...atatu.com>
To: Jiri Pirko <jiri@...nulli.us>, Thomas Graf <tgraf@...g.ch>
CC: John Fastabend <john.fastabend@...il.com>,
Pablo Neira Ayuso <pablo@...filter.org>,
simon.horman@...ronome.com, sfeldma@...il.com,
netdev@...r.kernel.org, davem@...emloft.net, gerlitz.or@...il.com,
andy@...yhouse.net, ast@...mgrid.com
Subject: Re: [net-next PATCH v3 00/12] Flow API
I am not big on high fives but here's my +1
Excellent diagram below.
cheers,
jamal
On 01/23/15 11:16, Jiri Pirko wrote:
>
> As I wrote earlier, the value is that userspace can easily use single
> xflows api to take care of all ways to handle flows (ovs kernel dp,
> rocker, other device, u32 tc filter + actions, you name it)
>
>
> my flow managing app
> |
> uspc |
> --------|----------------------------------------------------
> krnl |
> tc xflows api
> | | |
> | | ---------------------------------------------------
> | | |
> | ------------------ other xflows backend
> | |
> ovs xflows backend rocker driver xflows backend
> | |
> ovs dp |
> krnl |
> ----------------------------|--------------------------------
> hw |
> rocker switch
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists