-
Notifications
You must be signed in to change notification settings - Fork 522
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bufferorch][201911] Handle DEL_COMMAND for BUFFER_PG and BUFFER_QUEUE table #1787
Conversation
LGTM failed due to a compiling error which didn't happen on my local server. Will retry.
|
I think this is a known issue with 201911. @abdosi ? |
I believe these flows should be verified by unit test/VS. can you please add? |
Ok. Will check it. |
VS test added. |
@neethajohn kindly reminder to review this PR |
Commenter does not have sufficient privileges for PR 1787 in repo Azure/sonic-swss |
/azpw run |
1 similar comment
/azpw run |
@abdosi kindly reminder. This is a bug fix that need to go into 201911 |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: Stephen Sun <stephens@nvidia.com>
Signed-off-by: Stephen Sun <stephens@nvidia.com>
d1d60bd
to
f18f5e3
Compare
…1837) Depends on #1787 What I did To reclaim reserved buffer. As the way to do it differs among vendors, the environment ASIC_VENDOR is passed to swss docker and will be loaded when buffermgrd starts. After that, buffermgrd will: Handle port admin down on Mellanox platform. Not apply lossless buffer PG to an admin-down port Remove lossless buffer PG (3-4) from a port when it is shut down. Readd lossless buffer PG (3-4) to a port when a port is started up. Why I did it To support reclaiming reserved buffer when a port is shut down on Mellanox platform. How I verified it Regression test and vs test. Signed-off-by: Stephen Sun <stephens@nvidia.com>
What I did Let's add swap memory setup support for sonic_installer command so it could run on devices with limited memory resources. How I did it Add the following new options to sonic_installer: * --skip-setup-swap: if present, will skip setup swap memory. * --swap-mem-size: this will change the swap memory size(the default swap size is 1024 MiB) * --total-mem-threshold: if the system total memory is less than the value passed to --total-mem-threshold(default 2048 MiB), sonic_installer will setup swap memory. * --available-mem-threshold: if the system available memory is less than the value passed to --available-mem-threshold(default 1200 MiB), sonic_installer will setup swap memory. Add class MutuallyExclusiveOption to check the mutually-exclusive relationship between options. Add class SWAPAllocator to support swap memory setup/remove functionalities. NOTE: when sonic_installer tries to setup swap, if the system disk free space is less than 4096 MiB, sonic_installer will not setup swap memory. How to verify it Run sonic_installer over devices with limited memory
What I did
Handle
DEL
command forBUFFER_PG
andBUFFER_QUEUE
table.Add vs test for
BUFFER_PG
andBUFFER_QUEUE
table handlingSigned-off-by: Stephen Sun stephens@nvidia.com
Why I did it
How I verified it
Manually test.
Details if related