On Mon, Mar 20, 2017 at 10:56:34AM +0200, Roi Dayan wrote:
>
>
> On 20/03/2017 10:33, Roi Dayan wrote:
> >
> >
> >On 16/03/2017 17:40, Simon Horman wrote:
> >>On Mon, Mar 13, 2017 at 03:36:50PM +0200, Roi Dayan wrote:
> >>>This patch series introduces rule offload functionality to dpif-netlink
>
On 3/17/2017 4:14 PM, Simon Horman wrote:
Hi again,
I think that once the TODO items above are resolved - both of which I have
provided some feedback on separately - some consideration should be given to
merging this patchset.
Any thoughts/comments on that? Roi just commented that he will
On 16/03/2017 17:40, Simon Horman wrote:
On Mon, Mar 13, 2017 at 03:36:50PM +0200, Roi Dayan wrote:
This patch series introduces rule offload functionality to dpif-netlink
via netdev ports new flow offloading API. The user can specify whether to
enable rule offloading or not via OVS
On Mon, Mar 13, 2017 at 03:36:50PM +0200, Roi Dayan wrote:
> This patch series introduces rule offload functionality to dpif-netlink
> via netdev ports new flow offloading API. The user can specify whether to
> enable rule offloading or not via OVS configuration. Netdev providers
> are able to
On 13/03/2017 20:38, Simon Horman wrote:
On Mon, Mar 13, 2017 at 03:36:50PM +0200, Roi Dayan wrote:
This patch series introduces rule offload functionality to dpif-netlink
via netdev ports new flow offloading API. The user can specify whether to
enable rule offloading or not via OVS
On Mon, Mar 13, 2017 at 03:36:50PM +0200, Roi Dayan wrote:
> This patch series introduces rule offload functionality to dpif-netlink
> via netdev ports new flow offloading API. The user can specify whether to
> enable rule offloading or not via OVS configuration. Netdev providers
> are able to