Skip to content

[7060] put docker partition in the ramdisk for 7060 #9152

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

Closed
wants to merge 3 commits into from

Conversation

yxieca
Copy link
Contributor

@yxieca yxieca commented Nov 2, 2021

Why I did it

7060 has 4GB hard drive and they cannot fit full image from 202012 branch.

How I did it

Put docker partition in ram so that we could install full image on 7060
Put /var/log partition back on harddrive with space saved from docker partition.

How to verify it

  1. One image can be installed.
  2. Can upgrade from first image to second image.
  3. warm reboot test passes (lag recovered increased from 60 to 76 seconds, still within budget)
  4. fast reboot test passes
  5. this change only affects 7060, 7060_qx still use harddrive for docker partition due to memory limitation.

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106

Signed-off-by: Ying Xie [email protected]

@yxieca yxieca marked this pull request as ready for review November 3, 2021 23:11
@yxieca yxieca requested a review from lguohan as a code owner November 3, 2021 23:11
@yxieca yxieca changed the title [7060/7050qx] put docker partition in the ramdisk for 7060 and 7050qx [7060] put docker partition in the ramdisk for 7060 Nov 3, 2021
@lguohan
Copy link
Collaborator

lguohan commented Nov 4, 2021

since this mainly affects fast reboot and warm reboot control plane down time, how much increase do we see without using ram v.s. using ram? what is the tolerance we have for fast reboot/warm reboot now on this platform?

@yxieca yxieca marked this pull request as draft November 15, 2021 16:14
@lguohan
Copy link
Collaborator

lguohan commented Nov 15, 2021

We discussed this subject. There is a PKRAM approach, however it was not merged in the kernel and we cannot really use it.
Meanwhile, there is an existing mechanism use the DRAM to simulate persistent memory to sustain kexec reboot, and that
has been in the kernel for a long time since Linux kernel 4.2.

Is it possible for someone to further investigate if this approach can be used.

[RFC 00/43] PKRAM: Preserved-over-Kexec RAM - Anthony Yznaga (kernel.org)

How to Emulate Persistent Memory Using Dynamic Random-access Memory... (intel.com)

@yxieca yxieca closed this Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants