On Fri, Jan 25, 2013 at 01:46:15PM +0900, Simon Horman wrote:
> On Wed, Jan 23, 2013 at 09:48:17AM -0800, Ben Pfaff wrote:
> > On Thu, Jan 17, 2013 at 09:42:29AM +0900, Simon Horman wrote:
> > > On Wed, Jan 16, 2013 at 01:59:21PM -0800, Ben Pfaff wrote:
> > > > On Tue, Jan 15, 2013 at 01:20:57PM +0
On Wed, Jan 23, 2013 at 09:48:17AM -0800, Ben Pfaff wrote:
> On Thu, Jan 17, 2013 at 09:42:29AM +0900, Simon Horman wrote:
> > On Wed, Jan 16, 2013 at 01:59:21PM -0800, Ben Pfaff wrote:
> > > On Tue, Jan 15, 2013 at 01:20:57PM +0900, Simon Horman wrote:
> > > > Optimise OpenFlow flow expiry by plac
On Thu, Jan 17, 2013 at 09:42:29AM +0900, Simon Horman wrote:
> On Wed, Jan 16, 2013 at 01:59:21PM -0800, Ben Pfaff wrote:
> > On Tue, Jan 15, 2013 at 01:20:57PM +0900, Simon Horman wrote:
> > > Optimise OpenFlow flow expiry by placing expirable flows on a list.
> > > This optimises scanning of flo
On Tue, Jan 22, 2013 at 12:51:45PM -0800, Ben Pfaff wrote:
> On Tue, Jan 22, 2013 at 09:35:01AM +0900, Simon Horman wrote:
> > On Thu, Jan 17, 2013 at 09:42:29AM +0900, Simon Horman wrote:
> > > On Wed, Jan 16, 2013 at 01:59:21PM -0800, Ben Pfaff wrote:
> > > > On Tue, Jan 15, 2013 at 01:20:57PM +0
On Tue, Jan 22, 2013 at 09:35:01AM +0900, Simon Horman wrote:
> On Thu, Jan 17, 2013 at 09:42:29AM +0900, Simon Horman wrote:
> > On Wed, Jan 16, 2013 at 01:59:21PM -0800, Ben Pfaff wrote:
> > > On Tue, Jan 15, 2013 at 01:20:57PM +0900, Simon Horman wrote:
> > > > Optimise OpenFlow flow expiry by p
On Thu, Jan 17, 2013 at 09:42:29AM +0900, Simon Horman wrote:
> On Wed, Jan 16, 2013 at 01:59:21PM -0800, Ben Pfaff wrote:
> > On Tue, Jan 15, 2013 at 01:20:57PM +0900, Simon Horman wrote:
> > > Optimise OpenFlow flow expiry by placing expirable flows on a list.
> > > This optimises scanning of flo
On Wed, Jan 16, 2013 at 01:59:21PM -0800, Ben Pfaff wrote:
> On Tue, Jan 15, 2013 at 01:20:57PM +0900, Simon Horman wrote:
> > Optimise OpenFlow flow expiry by placing expirable flows on a list.
> > This optimises scanning of flows for expiry in two ways:
> >
> > * Empirically list traversal appea
On Tue, Jan 15, 2013 at 01:20:57PM +0900, Simon Horman wrote:
> Optimise OpenFlow flow expiry by placing expirable flows on a list.
> This optimises scanning of flows for expiry in two ways:
>
> * Empirically list traversal appears faster than the code it replaces.
>
> With 1,000,000 flows pres
Optimise OpenFlow flow expiry by placing expirable flows on a list.
This optimises scanning of flows for expiry in two ways:
* Empirically list traversal appears faster than the code it replaces.
With 1,000,000 flows present an otherwise idle system I observed CPU
utilisation of around 20% wi
On Sun, Jan 13, 2013 at 09:22:31PM -0800, Ben Pfaff wrote:
> On Mon, Jan 14, 2013 at 10:06:13AM +0900, Simon Horman wrote:
> > Optimise OpenFlow flow expiry by placing expirable flows on a list.
> > This optimises scanning of flows for expiry in two ways:
> >
> > * Empirically list traversal appea
On Mon, Jan 14, 2013 at 10:06:13AM +0900, Simon Horman wrote:
> Optimise OpenFlow flow expiry by placing expirable flows on a list.
> This optimises scanning of flows for expiry in two ways:
>
> * Empirically list traversal appears faster than the code it replaces.
>
> With 1,000,000 flows pres
Optimise OpenFlow flow expiry by placing expirable flows on a list.
This optimises scanning of flows for expiry in two ways:
* Empirically list traversal appears faster than the code it replaces.
With 1,000,000 flows present an otherwise idle system I observed CPU
utilisation of around 20% wi
12 matches
Mail list logo