Re: [ovs-dev] [PATCH V3] ofproto-dpif-upcall: Remove the dispatcher thread.

2014-02-27 Thread Alex Wang
Thanks Han, I'm going to post them soon, gonna be in series. Alex Wang, On Wed, Feb 26, 2014 at 4:26 PM, Han Zhou wrote: > Hi Alex, > > I had a simple test with your V3 patch, and the improvements are > obvious. > > In my 32 core machine I ran 10 handler threads, comparing hping3 test > resul

Re: [ovs-dev] [PATCH V3] ofproto-dpif-upcall: Remove the dispatcher thread.

2014-02-27 Thread Alex Wang
Thanks very much for the review!~ ;D Please see my reply inline, On Thu, Feb 20, 2014 at 3:25 PM, Pravin Shelar wrote: > > upcall.cmd = OVS_PACKET_CMD_MISS; > > upcall.key = &key; > > upcall.userdata = NULL; > > - upcall.portid = p

Re: [ovs-dev] [PATCH V3] ofproto-dpif-upcall: Remove the dispatcher thread.

2014-02-20 Thread Pravin Shelar
On Tue, Feb 18, 2014 at 10:52 AM, Alex Wang wrote: > This commit removes the 'dispatcher' thread by allowing 'handler' > threads to read upcalls directly from dpif. vport in dpif will > open netlink sockets for each handler and will use the 5-tuple > hash from the missed packet to choose which so

Re: [ovs-dev] [PATCH V3] ofproto-dpif-upcall: Remove the dispatcher thread.

2014-02-19 Thread Alex Wang
Thanks a lot for pointing it out, Yamamoto, I failed to cover this. will work on solving it. Alex Wang, On Wed, Feb 19, 2014 at 6:36 PM, YAMAMOTO Takashi wrote: > > This commit removes the 'dispatcher' thread by allowing 'handler' > > threads to read upcalls directly from dpif. vport in dpif

Re: [ovs-dev] [PATCH V3] ofproto-dpif-upcall: Remove the dispatcher thread.

2014-02-19 Thread YAMAMOTO Takashi
> This commit removes the 'dispatcher' thread by allowing 'handler' > threads to read upcalls directly from dpif. vport in dpif will > open netlink sockets for each handler and will use the 5-tuple > hash from the missed packet to choose which socket (handler) to > send the upcall. > > This patch