-
Notifications
You must be signed in to change notification settings - Fork 264
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
add logic to stack lcow layers on a single VPMEM device #930
Conversation
f3ddb24
to
5459050
Compare
9c8e6fe
to
3c00b47
Compare
710fdcb
to
bca9a89
Compare
bca9a89
to
a98df30
Compare
It might be good if you could make an issue on hcsshim for this and describe the memory allocation method and any other additional big changes proposed here. |
727b0ac
to
a5cb324
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
couple of non blocking nits, otherwise LGTM
4f78a97
to
f29620b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fixes, LGTM again :)
f29620b
to
59a90b5
Compare
add VirtualPMemMapping schema and update gcs types add memory allocator interface and implementation VPMem multi-mapping support has been added in 19H1, which enables packing multiple VHDs onto a single VPMem device. This feature enables an optimization, where multiple LCOW container layers can be packed onto a single VPMem device. This change uses memory allocator introduced above to keep track of the VPMem surface allocation. Additionally, introduce new structs to keep track of the internal state of each mapped LCOW layer VHD and update HCS/GCS calls accordingly. The optimization is enabled by default on supported systems and fall-back to old behavior otherwise. add CRI tests Signed-off-by: Maksim An <maksiman@microsoft.com>
59a90b5
to
9ed9300
Compare
The force push was fixing some edgecases I think you said this morning? |
yeah, I added one more test case to cover rootfs.vhd vs initrd (it was defaulting to only do rootfs) |
This was left behind due to an unlucky conflict between microsoft#1004 and microsoft#930. The file already existed with the same content at the new location, and nothing was referencing this location, so a trivial deletion. Signed-off-by: Paul "TBBle" Hampson <Paul.Hampson@Pobox.com>
Related work items: microsoft#930, microsoft#962, microsoft#1004, microsoft#1008, microsoft#1039, microsoft#1045, microsoft#1046, microsoft#1047, microsoft#1052, microsoft#1053, microsoft#1054, microsoft#1057, microsoft#1058, microsoft#1060, microsoft#1061, microsoft#1063, microsoft#1064, microsoft#1068, microsoft#1069, microsoft#1070, microsoft#1071, microsoft#1074, microsoft#1078, microsoft#1079, microsoft#1081, microsoft#1082, microsoft#1083, microsoft#1084, microsoft#1088, microsoft#1090, microsoft#1091, microsoft#1093, microsoft#1094, microsoft#1096, microsoft#1098, microsoft#1099, microsoft#1102, microsoft#1103, microsoft#1105, microsoft#1106, microsoft#1108, microsoft#1109, microsoft#1115, microsoft#1116, microsoft#1122, microsoft#1123, microsoft#1126
…pper add logic to stack lcow layers on a single VPMEM device
This was left behind due to an unlucky conflict between microsoft#1004 and microsoft#930. The file already existed with the same content at the new location, and nothing was referencing this location, so a trivial deletion. Signed-off-by: Paul "TBBle" Hampson <Paul.Hampson@Pobox.com>
This PR adds logic to reuse an existing VPMEM device and stack multiple LCOW layers onto it.
The change depends on microsoft/opengcs#389
More background in #940
Signed-off-by: Maksim An maksiman@microsoft.com