@@ -360,6 +360,21 @@ devices to bridge ``br0``. Once complete, follow the below steps:
$ cat /proc/interrupts | grep virtio
+Ingress Scheduling
+------------------
+
+The ingress scheduling feature is described in general in
+``ovs-vswitchd.conf.db (5)``.
+
+Ingress scheduling currently supports setting a priority for incoming packets
+for an entire interface. Priority levels 0 (lowest) to 3 (highest) are
+supported. The default priority is 0.
+
+To prioritize packets on a particular port:
+
+ $ ovs-vsctl set Interface dpdk0 \
+ ingress_sched=port_prio=3
+
.. _dpdk-flow-hardware-offload:
Flow Hardware Offload (Experimental)
@@ -3196,6 +3196,21 @@ ovs-vsctl add-port br0 p0 -- set Interface p0 type=patch options:peer=p1 \
</column>
</group>
+ <group title="Ingress Scheduling">
+ <p>
+ Configuration to allow rxd traffic to be prioritized on a per Interface
+ basis.
+ </p>
+ <column name="other_config" key="port_prio">
+ <p>
+ The ingress priority of the port: 0 (lowest) to 3 (highest). Higher
+ priority ports are read more frequently than lower priority ports.
+ This provides enhanced protection to packets ingressing high priority
+ ports against being dropped due to Rx queue overflow.
+ </p>
+ </column>
+ </group>
+
<group title="Bidirectional Forwarding Detection (BFD)">
<p>
BFD, defined in RFC 5880 and RFC 5881, allows point-to-point
Signed-off-by: Billy O'Mahony <billy.o.mahony@intel.com> --- Documentation/howto/dpdk.rst | 15 +++++++++++++++ vswitchd/vswitch.xml | 15 +++++++++++++++ 2 files changed, 30 insertions(+)