Subject: Re: [net-next PATCH v3 00/12] Flow API

From: Jamal Hadi Salim <[email-masked]>
Date: Sat, 24 Jan 2015 08:04:42 -0500

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
>