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 <echau...@redhat.com>
Signed-off-by: Simon Horman <ho...@ovn.org>
---
Changes in v2
* Added Eelco's ack
---
Documentation/tutorials/faucet.rst | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/Documentation/tutorials/faucet.rst
b/Documentation/tutorials/faucet.rst
index 33e4543e4023..62d3f5070f14 100644
--- a/Documentation/tutorials/faucet.rst
+++ b/Documentation/tutorials/faucet.rst
@@ -768,11 +768,10 @@ way, performance would be terrible. The key to getting
high
performance from this architecture is caching. Open vSwitch includes
a multi-level cache. It works like this:
-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
- first-level cache called the "microflow cache". The microflow
- cache is the key to performance for relatively long-lived, high
- packet rate flows. If the datapath has a microflow cache, then it
+1. A packet initially arrives at the datapath. Some datapaths, such
+ as DPDK, have a first-level cache called the "microflow cache". The
+ microflow cache is the key to performance for relatively long-lived,
+ high 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
associated actions. Otherwise, it proceeds to step 2.
--
2.47.2
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
