Thu, Sep 04, 2014 at 10:46:28PM CEST, pshe...@nicira.com wrote:
On Thu, Sep 4, 2014 at 5:33 AM, Jiri Pirko j...@resnulli.us wrote:
Wed, Sep 03, 2014 at 08:41:39PM CEST, pshe...@nicira.com wrote:
On Wed, Sep 3, 2014 at 2:24 AM, Jiri Pirko j...@resnulli.us wrote:
After this, flow related
On Wed, Sep 17, 2014 at 1:34 AM, Jiri Pirko j...@resnulli.us wrote:
Thu, Sep 04, 2014 at 10:46:28PM CEST, pshe...@nicira.com wrote:
On the other hand if vswitchd uses common interface (switchdev) there
is no need to extend ovs kernel interface. For example specifying
extra metadata, like (sw
Wed, Sep 03, 2014 at 05:20:25PM CEST, john.fastab...@gmail.com wrote:
On 09/03/2014 02:24 AM, Jiri Pirko wrote:
After this, flow related structures can be used in other code.
Signed-off-by: Jiri Pirko j...@resnulli.us
---
Hi Jiri,
As I indicated before I'm looking into integrating this with
Wed, Sep 03, 2014 at 08:42:18PM CEST, pshe...@nicira.com wrote:
On Wed, Sep 3, 2014 at 8:20 AM, John Fastabend john.fastab...@gmail.com
wrote:
On 09/03/2014 02:24 AM, Jiri Pirko wrote:
After this, flow related structures can be used in other code.
Signed-off-by: Jiri Pirko j...@resnulli.us
Wed, Sep 03, 2014 at 08:41:39PM CEST, pshe...@nicira.com wrote:
On Wed, Sep 3, 2014 at 2:24 AM, Jiri Pirko j...@resnulli.us wrote:
After this, flow related structures can be used in other code.
Signed-off-by: Jiri Pirko j...@resnulli.us
---
include/net/sw_flow.h | 99
On Thu, Sep 4, 2014 at 5:33 AM, Jiri Pirko j...@resnulli.us wrote:
Wed, Sep 03, 2014 at 08:41:39PM CEST, pshe...@nicira.com wrote:
On Wed, Sep 3, 2014 at 2:24 AM, Jiri Pirko j...@resnulli.us wrote:
After this, flow related structures can be used in other code.
Signed-off-by: Jiri Pirko
On 09/03/2014 02:24 AM, Jiri Pirko wrote:
After this, flow related structures can be used in other code.
Signed-off-by: Jiri Pirko j...@resnulli.us
---
Hi Jiri,
As I indicated before I'm looking into integrating this with some
hardware here. Progress is a bit slow but starting to look at
On Wed, Sep 3, 2014 at 2:24 AM, Jiri Pirko j...@resnulli.us wrote:
After this, flow related structures can be used in other code.
Signed-off-by: Jiri Pirko j...@resnulli.us
---
include/net/sw_flow.h | 99 ++
net/openvswitch/actions.c | 3 +-
On Wed, Sep 3, 2014 at 8:20 AM, John Fastabend john.fastab...@gmail.com wrote:
On 09/03/2014 02:24 AM, Jiri Pirko wrote:
After this, flow related structures can be used in other code.
Signed-off-by: Jiri Pirko j...@resnulli.us
---
Hi Jiri,
As I indicated before I'm looking into
On Wed, Sep 3, 2014 at 2:22 PM, Jamal Hadi Salim j...@mojatatu.com wrote:
On 09/03/14 14:41, Pravin Shelar wrote:
On Wed, Sep 3, 2014 at 2:24 AM, Jiri Pirko j...@resnulli.us wrote:
HW offload API should be separate from OVS module.
The above part i agree with. Infact it is very odd that
On 09/03/14 17:59, Pravin Shelar wrote:
Both of us are saying same thing.
What I meant was for OVS use-case, where OVS wants to use offload for
switching flows, vswitchd userspace process can program HW offload
using kernel HW offload APIs directly from userspace, rather than
going through OVS
11 matches
Mail list logo
