mirror of
https://github.com/openvswitch/ovs
synced 2025-08-22 09:58:01 +00:00
docs: faucet: Remove references to OOT kernel module.
Remove documentation relating to OOT kernel module. It is out-of-tree (OOT) with respect to the upstream kernel. But in this document referred to as in-tree, with respect to the Open vSwitch tree. Support for the OOT module was removed in the v3.0 release of Open vSwitch. And is now no longer supported by any maintained versions of Open vSwitch. Acked-by: Eelco Chaudron <echaudro@redhat.com> Signed-off-by: Simon Horman <horms@ovn.org>
This commit is contained in:
parent
89e8c12499
commit
aea939b24a
@ -768,11 +768,10 @@ way, performance would be terrible. The key to getting high
|
|||||||
performance from this architecture is caching. Open vSwitch includes
|
performance from this architecture is caching. Open vSwitch includes
|
||||||
a multi-level cache. It works like this:
|
a multi-level cache. It works like this:
|
||||||
|
|
||||||
1. A packet initially arrives at the datapath. Some datapaths (such
|
1. A packet initially arrives at the datapath. Some datapaths, such
|
||||||
as DPDK and the in-tree version of the OVS kernel module) have a
|
as DPDK, have a first-level cache called the "microflow cache". The
|
||||||
first-level cache called the "microflow cache". The microflow
|
microflow cache is the key to performance for relatively long-lived,
|
||||||
cache is the key to performance for relatively long-lived, high
|
high packet rate flows. If the datapath has a microflow cache, then it
|
||||||
packet rate flows. If the datapath has a microflow cache, then it
|
|
||||||
consults it and, if there is a cache hit, the datapath executes the
|
consults it and, if there is a cache hit, the datapath executes the
|
||||||
associated actions. Otherwise, it proceeds to step 2.
|
associated actions. Otherwise, it proceeds to step 2.
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user