Code Review / vpp.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: c7886c5) | patch
Perf tune get_frame_size_info 60/18160/3
authorDave Barach <dbarach@cisco.com>
Sun, 10 Mar 2019 13:44:51 +0000 (09:44 -0400)
committerFlorin Coras <florin.coras@gmail.com>
Sun, 10 Mar 2019 23:16:43 +0000 (23:16 +0000)
commit593eedf2561f639703d366cd21ab0c3ae03bdb0c
tree75c7ed53b941d46127d1c6b88a16f5936570d2cetree | snapshot
parentc7886c5d50782b9653ab41772fb93cff0c0ad9dacommit | diff
Perf tune get_frame_size_info

It turns out that for scalar sizes 0..24, frames are always the same
size. That range includes all current use-cases - and then some - so
get rid of the hash table. Old code preserved under #ifdef
VLIB_SUPPORTS_ARBITRARY_SCALAR_SIZES.

Change-Id: Ic005c7143c9639f77d1a0fadd2fc0e90dccb68c1
Signed-off-by: Dave Barach <dbarach@cisco.com>
src/vlib/main.c diff | blob | history
src/vlib/node.c diff | blob | history
src/vlib/threads.c diff | blob | history
Vector Packet Processing