> On Jan 11, 2016, at 9:35 AM, Ben Pfaff wrote:
>
> On Mon, Dec 21, 2015 at 11:38:33PM -0800, Ben Pfaff wrote:
>> On Mon, Nov 30, 2015 at 10:03:11AM -0800, Jarno Rajahalme wrote:
>>>
On Nov 29, 2015, at 17:12, Ben Pfaff wrote:
> On Mon, Nov 23, 2015 at 08:54:31PM -0800, Jarno Ra
On Mon, Dec 21, 2015 at 11:38:33PM -0800, Ben Pfaff wrote:
> On Mon, Nov 30, 2015 at 10:03:11AM -0800, Jarno Rajahalme wrote:
> >
> > > On Nov 29, 2015, at 17:12, Ben Pfaff wrote:
> > >
> > >> On Mon, Nov 23, 2015 at 08:54:31PM -0800, Jarno Rajahalme wrote:
> > >> Back by popular demand, here is
On Mon, Nov 30, 2015 at 10:03:11AM -0800, Jarno Rajahalme wrote:
>
> > On Nov 29, 2015, at 17:12, Ben Pfaff wrote:
> >
> >> On Mon, Nov 23, 2015 at 08:54:31PM -0800, Jarno Rajahalme wrote:
> >> Back by popular demand, here is the OpenFlow meter implementation for
> >> the userspace datapath. Me
> On Nov 29, 2015, at 17:12, Ben Pfaff wrote:
>
>> On Mon, Nov 23, 2015 at 08:54:31PM -0800, Jarno Rajahalme wrote:
>> Back by popular demand, here is the OpenFlow meter implementation for
>> the userspace datapath. Meters are inherently shared datapath
>> resources and this version uses a simp
On Mon, Nov 23, 2015 at 08:54:31PM -0800, Jarno Rajahalme wrote:
> Back by popular demand, here is the OpenFlow meter implementation for
> the userspace datapath. Meters are inherently shared datapath
> resources and this version uses a simple locking strategy which may
> not be optimal for DPDK.
Back by popular demand, here is the OpenFlow meter implementation for
the userspace datapath. Meters are inherently shared datapath
resources and this version uses a simple locking strategy which may
not be optimal for DPDK. Nonetheless, this implementation should be a
good starting point for fur
