Differences

This shows you the differences between two versions of the page.

--- oracle:linux_networking_configuration [2020/11/30 23:39] – hvillanueva
+++ oracle:linux_networking_configuration [2020/11/30 23:41] (current) – hvillanueva
@@ Line 86: / Line 86: @@
 {{:oracle:linux_networking_configuration_16_-_hvillanueva.png?600|}}
+===== dev_weight =====
+The maximum number of packets that kernel can handle on a NAPI interrupt, it's a Per-CPU variable. For drivers that support LRO or GRO_HW, a hardware aggregated packet is counted as one packet in this context. Default: 64
+Generic Receive Offload (GRO) is a widely used SW-based offloading technique to reduce per-packet processing overheads. By reassembling small packets into larger ones, GRO enables applications to process fewer large packets directly, thus reducing the number of packets to be processed. To benefit DPDK-based applications, like Open vSwitch, DPDK also provides own GRO implementation. In DPDK, GRO is implemented as a standalone library. Applications explicitly use the GRO library to reassemble packets.
+==== 2. network_throughput_test.sh Script ====
+PURPOSE
+This troubleshooting note aims to identify the theoretical network throughput between a Protected Database system and a Zero Data Loss Recovery Appliance, or between two Zero Data Loss Recovery Appliances in a replication configuration.
+TROUBLESHOOTING STEPS
+Assumptions
+This script uses the QPERF utility that is provided as part of an Exadata Engineered System as well as part of the Zero Data Loss Recovery Appliance.
+This script may be executed from any Linux server with a BASH shell, and requires trusted SSH to be established between the execution node and the two sets of nodes that are being tested.
+The Execution node may be one of the nodes being tested.
+The O/S user used for trusted SSH is the O/S user running the script. There is no support for the script to use a different O/S user for logging into the nodes being tested.
+Installation
+If not already available under /opt/oracle.RecoveryAppliance/client then download the script attached to this MOS Note and copy it to the desired location.