On Thu, Dec 12, 2013 at 01:39:04PM -0800, Ethan Jackson wrote:
> > Hmm. Using too many could easily cause a crash, but at least it would
> > recover after restarting when the number was lowered again.
>
> Interesting, why would we crash? Memory consumption? At any rate,
> this is the kind of th
> Hmm. Using too many could easily cause a crash, but at least it would
> recover after restarting when the number was lowered again.
Interesting, why would we crash? Memory consumption? At any rate,
this is the kind of thing where you have to go out of your way to get
it wrong, so I'm fine wit
On Sun, Dec 08, 2013 at 06:45:10PM -0800, Ethan Jackson wrote:
> There's no particular reason to limit the number of handler threads to
> 64. If someone wants to try more, let them.
>
> Signed-off-by: Ethan Jackson
Hmm. Using too many could easily cause a crash, but at least it would
recover a
There's no particular reason to limit the number of handler threads to
64. If someone wants to try more, let them.
Signed-off-by: Ethan Jackson
---
ofproto/ofproto-dpif-upcall.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/ofproto/ofproto-dpif-upcall.c b/ofproto/ofproto-dpif-upcall.c
inde
