datapath: An expanded table should be larger than its predecessor
authorSimon Horman <horms@verge.net.au>
Tue, 12 Jul 2011 06:52:44 +0000 (15:52 +0900)
committerBen Pfaff <blp@nicira.com>
Tue, 12 Jul 2011 16:20:18 +0000 (09:20 -0700)
commitbd6ce3f24b740fc946fe88baa0619c945f02b434
treeb239f6b57670f235608a724e4f258c945fc0405e
parentb90546d40ecf15fdeb0c82f31b6a8283fb3f386e
datapath: An expanded table should be larger than its predecessor

This resolves what appears to be a think-o in tbl_expand()

* Old Logic: Always create tables with TBL_MIN_BUCKETS buckets
* New Logic: Create tables twice as big as their predecessor

When sending 10,000 flows through ovs-vswitchd:
* Old Logic: CPU bound in tbl_lookup(), significant packet loss
* New Logic: ~10% of one core used, negligible packet loss

Tested with an Intel E5520 @ 2.27GHz,
flows from an ethernet device to to a dummy interface with
no address configured.

Signed-off-by: Simon Horman <horms@verge.net.au>
Signed-off-by: Jesse Gross <jesse@nicira.com>
datapath/table.c