Re: [oss-drivers] Re: [PATCH net-next v2 7/9] nfp: add metadata to each flow offload

2017-06-29 Thread Simon Horman
On Thu, Jun 29, 2017 at 01:42:50AM -0700, Jakub Kicinski wrote: > On Thu, 29 Jun 2017 10:14:29 +0200, Simon Horman wrote: > > > > + /* Checking if buffer is empty. */ > > > > + if (ring->head == ring->tail) { > > > > + *mask_id = freed_id; > > > > + return -E

Re: [oss-drivers] Re: [PATCH net-next v2 7/9] nfp: add metadata to each flow offload

2017-06-29 Thread Jakub Kicinski
On Thu, 29 Jun 2017 10:14:29 +0200, Simon Horman wrote: > > > + /* Checking if buffer is empty. */ > > > + if (ring->head == ring->tail) { > > > + *mask_id = freed_id; > > > + return -ENOENT; > > > + } > > > + > > > + memcpy(&temp_id, &ring->buf[ring->tail], NFP_FLOWER_MASK_ELEMENT_

Re: [oss-drivers] Re: [PATCH net-next v2 7/9] nfp: add metadata to each flow offload

2017-06-29 Thread Simon Horman
On Wed, Jun 28, 2017 at 07:33:02PM -0700, Jakub Kicinski wrote: > On Wed, 28 Jun 2017 22:30:00 +0200, Simon Horman wrote: > > From: Pieter Jansen van Vuuren > > > > Adds metadata describing the mask id of each flow and keeps track of > > flows installed in hardware. Previously a flow could not be

Re: [PATCH net-next v2 7/9] nfp: add metadata to each flow offload

2017-06-28 Thread Jakub Kicinski
On Wed, 28 Jun 2017 22:30:00 +0200, Simon Horman wrote: > From: Pieter Jansen van Vuuren > > Adds metadata describing the mask id of each flow and keeps track of > flows installed in hardware. Previously a flow could not be removed > from hardware as there was no way of knowing if that a specific

[PATCH net-next v2 7/9] nfp: add metadata to each flow offload

2017-06-28 Thread Simon Horman
From: Pieter Jansen van Vuuren Adds metadata describing the mask id of each flow and keeps track of flows installed in hardware. Previously a flow could not be removed from hardware as there was no way of knowing if that a specific flow was installed. This is solved by storing the offloaded flows