Set sock rx Buf size to 3MB. #5566
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lguohan
reviewed
Oct 8, 2020
| @@ -34,6 +34,6 @@ net.ipv6.conf.all.keep_addr_on_down=1 | |||
| net.ipv6.conf.eth0.keep_addr_on_down=1 | |||
| net.ipv4.tcp_l3mdev_accept=1 | |||
| net.ipv4.udp_l3mdev_accept=1 | |||
| net.core.rmem_max=2097152 | |||
| net.core.rmem_max=3145728 | |||
| net.core.wmem_max=2097152 | |||
There was a problem hiding this comment.
do we need to update the wmem?
There was a problem hiding this comment.
I think we can increase both values
There was a problem hiding this comment.
We can increase the send buffer size to 3M. Updated PR with the changes.
lguohan
approved these changes
Oct 14, 2020
prsunny
approved these changes
Oct 15, 2020
|
in 201911 branch images sometimes see netlink out of memory error log, it would be good to cherry-pick this to 201911 |
|
@abdosi would you please help to cherry-pick this to 201911? |
abdosi
pushed a commit
that referenced
this pull request
Nov 24, 2020
* Set sock rx Buf size to 3MB.
santhosh-kt
pushed a commit
to santhosh-kt/sonic-buildimage
that referenced
this pull request
Feb 25, 2021
* Set sock rx Buf size to 3MB.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
- Why I did it
netlink out of memory seen for 8K neighbor updates.
- How I did it
Config IP to 2 interfaces connected to ixia. Ethernet1 (21.0.0.1/16) and Ethernet4 (24.1.1.1/24)
DUT copp rules are as ARP CIR=2000 and IP2ME CIR=6000
Start Continuous Traffic (5G) is started from ixia connected to Ethernet4 with the DIP matching with the 8K ARP Host Range before learning ARP entries. These traffic will be software forwarded from linux kernel.
DUT is configured to learn ARP through ARP Reply packets
echo 1 > /proc/sys/net/ipv4/conf/Ethernet1/arp_accept
Start continuous ARP Reply Packet is sent from IXIA connected to Ethernet1 Port at 2K Packet/Secs with Host IP starting from 20.20.0.2 and Incrementing for 8K.
After step (5), expectation is all 5G traffic must be forwarded from ASIC but not all NEIGH entries are updated to APP_DB and ASIC_DB because of out of memory error.
- How to verify it
- Which release branch to backport (provide reason below if selected)
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)