On 05/01/2014 06:09 PM, Zoltan Kiss wrote:
On 29/04/14 17:36, Thomas Graf wrote:
On Tue, Apr 29, 2014 at 05:17:07PM +0100, Zoltan Kiss wrote:
On 23/04/14 22:56, Thomas Graf wrote:
On 04/23/2014 10:12 PM, Ethan Jackson wrote:
The problem has actually gotten worse since we've gotten rid of the
On 04/29/2014 09:47 PM, Ethan Jackson wrote:
The common use case is a flow expiring during the lifetime of a TCP
connection. It will result in multiple data packets being sent upwards.
It's much less likely in the megaflows era though.
I think this is pretty unlikely except in some extreme circ
On 29/04/14 17:36, Thomas Graf wrote:
On Tue, Apr 29, 2014 at 05:17:07PM +0100, Zoltan Kiss wrote:
On 23/04/14 22:56, Thomas Graf wrote:
On 04/23/2014 10:12 PM, Ethan Jackson wrote:
The problem has actually gotten worse since we've gotten rid of the
dispatcher thread. Now each thread has it's
> The common use case is a flow expiring during the lifetime of a TCP
> connection. It will result in multiple data packets being sent upwards.
> It's much less likely in the megaflows era though.
I think this is pretty unlikely except in some extreme circumstances.
For a flow to be removed from t
On Tue, Apr 29, 2014 at 05:17:07PM +0100, Zoltan Kiss wrote:
> On 23/04/14 22:56, Thomas Graf wrote:
> >On 04/23/2014 10:12 PM, Ethan Jackson wrote:
> >>The problem has actually gotten worse since we've gotten rid of the
> >>dispatcher thread. Now each thread has it's own channel per port.
> >>
>
On 23/04/14 22:56, Thomas Graf wrote:
On 04/23/2014 10:12 PM, Ethan Jackson wrote:
The problem has actually gotten worse since we've gotten rid of the
dispatcher thread. Now each thread has it's own channel per port.
I wonder if the right approach is to simply ditch the per-port
fairness in th
On 04/23/2014 10:12 PM, Ethan Jackson wrote:
The problem has actually gotten worse since we've gotten rid of the
dispatcher thread. Now each thread has it's own channel per port.
I wonder if the right approach is to simply ditch the per-port
fairness in the case where mmap netlink is enabled.
The problem has actually gotten worse since we've gotten rid of the
dispatcher thread. Now each thread has it's own channel per port.
I wonder if the right approach is to simply ditch the per-port
fairness in the case where mmap netlink is enabled. I.E. we simply
have one channel per thread and
