SMC cache was introduced in 2.10 with experimental tag. SMC cache is a layer of software cache located after EMC cache. The purpose is to improve the performance of use cases that many flows missing the EMC cache.
One can enable SMC cache using smc-enable=true option. Signed-off-by: Yipeng Wang <yipeng1.w...@intel.com> --- Documentation/topics/dpdk/bridge.rst | 6 +++--- NEWS | 1 + 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/Documentation/topics/dpdk/bridge.rst b/Documentation/topics/dpdk/bridge.rst index a3ed926..4ca79a4 100644 --- a/Documentation/topics/dpdk/bridge.rst +++ b/Documentation/topics/dpdk/bridge.rst @@ -117,15 +117,15 @@ It is also possible to enable/disable EMC on per-port basis using:: For more information on the EMC refer to :doc:`/intro/install/dpdk` . -SMC cache (experimental) -------------------------- +SMC cache +--------- SMC cache or signature match cache is a new cache level after EMC cache. The difference between SMC and EMC is SMC only stores a signature of a flow thus it is much more memory efficient. With same memory space, EMC can store 8k flows while SMC can store 1M flows. When traffic flow count is much larger than EMC size, it is generally beneficial to turn off EMC and turn on SMC. It is -currently turned off by default and an experimental feature. +currently turned off by default. To turn on SMC:: diff --git a/NEWS b/NEWS index 806e3c8..feae994 100644 --- a/NEWS +++ b/NEWS @@ -34,6 +34,7 @@ Post-v2.11.0 * 'ovs-appctl exit' now implies cleanup of non-internal ports in userspace datapath regardless of '--cleanup' option. Use '--cleanup' to remove internal ports too. + * Removed experimental tag for SMC cache. - OVSDB: * OVSDB clients can now resynchronize with clustered servers much more quickly after a brief disconnection, saving bandwidth and CPU time. -- 2.7.4 _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev