Skip to content

Commit be8957c

Browse files
author
Traci Morrison
authored
Merge pull request #7269 from tmorriso-rh/PR-5049-IPSec-statement
Fixed incorrect statement about IPSec throughput
2 parents aae6676 + 95811fd commit be8957c

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

scaling_performance/network_optimization.adoc

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -58,8 +58,8 @@ in latency tests.
5858
[[scaling-performance-optimizing-mtu]]
5959
=== Optimizing the MTU for Your Network
6060

61-
There are two MTUs (maximum transmission units) that matter: the network
62-
interface card (NIC) MTU, and the SDN overlay's MTU.
61+
There are two important maximum transmission units (MTUs): the network
62+
interface card (NIC) MTU and the SDN overlay's MTU.
6363

6464
The NIC MTU must be less than or equal to the maximum supported value of the NIC
6565
of your network. If you are optimizing for throughput, pick the largest possible
@@ -97,7 +97,7 @@ can also be set to any other CNI-compatible plug-in as well.
9797
default values allow for:
9898

9999
- Maximum cluster size of 1024 nodes
100-
- Each of the 1024 nodes has a /23 allocated to it (510 usable IPs for pods)
100+
- Each of the 1024 nodes has a /23 allocated to it (510 usable IP addresses for pods)
101101
- Provides 65,536 IP addresses for services.
102102

103103
Under most circumstances, these networks cannot be changed after deployment. Thus it is important to plan ahead for growth.
@@ -114,7 +114,7 @@ Ansible inventory file:
114114
osm_cluster_network_cidr=10.128.0.0/10
115115
----
116116

117-
This will allow for 8192 nodes, each with 510 usable IPs.
117+
This will allow for 8192 nodes, each with 510 usable IP addresses.
118118

119119
See the supportability limits in the {product-title} documentation for node/pod limits for the version of software you are installing.
120120

@@ -125,6 +125,7 @@ Because encrypting and decrypting node hosts uses CPU power, performance is
125125
affected both in throughput and CPU usage on the nodes when encryption is
126126
enabled, regardless of the IP security system being used.
127127

128-
IPSec encrypts traffic at the IP level, before it hits the NIC, protecting
128+
IPSec encrypts traffic at the IP payload level, before it hits the NIC, protecting
129129
fields that would otherwise be used for NIC offloading. This means that some NIC
130-
acceleration features may not be usable when IPSec is enabled and will lead to increased throughput and CPU usage.
130+
acceleration features may not be usable when IPSec is enabled and will lead to
131+
decreased throughput and increased CPU usage.

0 commit comments

Comments
 (0)