Re: [ovs-dev] [RFC 00/14] Revalidate flows with unique identifiers.

2014-08-22 Thread Joe Stringer
Hi Jarno, There's been a few iterations. The previous 64-bit version was using a 32-bit hash combined with a thread ID. The 128-bit hash was based on a suggestion to have sufficient bits to randomly generate the identifiers, however I've since shifted to using the hash of the flow key---This allo

Re: [ovs-dev] [RFC 00/14] Revalidate flows with unique identifiers.

2014-08-21 Thread Jarno Rajahalme
Joe, What was the reason to go from 64-bit hash to 128-bit hash? Jarno > On Aug 20, 2014, at 10:41 PM, Joe Stringer wrote: > > One of the current bottlenecks for revalidation performance is the cost of > assembling flow keys, masks and actions in the (linux) datapath. This series > seeks to

[ovs-dev] [RFC 00/14] Revalidate flows with unique identifiers.

2014-08-20 Thread Joe Stringer
One of the current bottlenecks for revalidation performance is the cost of assembling flow keys, masks and actions in the (linux) datapath. This series seeks to reduce this cost by caching these elements in the udpif, and modifying the datapath to skip sending these. To distinguish flows in the dat