Skip to content
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

adopting cgroup2 in coreclr #854

Closed
Maoni0 opened this issue Jul 22, 2019 · 11 comments
Closed

adopting cgroup2 in coreclr #854

Maoni0 opened this issue Jul 22, 2019 · 11 comments

Comments

@Maoni0
Copy link
Member

Maoni0 commented Jul 22, 2019

from corefx 39673, cgroup2 is out. @janvorli would you please take a look at cgroup2 and see if it's a simple matter of adopting it (eg, read the same values just from different places kind of thing) or does it mean we'll need to handle new scenarios enabled by cgroup2 and/or does it make us change anything we are currently doing?

@omajid
Copy link
Member

omajid commented Jul 23, 2019

From skimming the docs (https://www.kernel.org/doc/Documentation/cgroup-v2.txt) and browsing through some presentations (slides 1, slides 2) it looks like cgroups v2 is mostly a cleanup. I am not an expert, but I didn't see any new features. The only thing that caught my eye was better support for notifications, including memory events.

@omajid
Copy link
Member

omajid commented Jul 23, 2019

FWIW, I intend to contribute the changes for cgroupv2 support in coreclr (unless someone else does it before me).

@Maoni0
Copy link
Member Author

Maoni0 commented Jul 23, 2019

that's wonderful to hear; thanks @omajid!

@omajid
Copy link
Member

omajid commented Jul 26, 2019

Happy to help!

I did hit a bit of a roadblock. I could use some advice about tests on https://github.com/dotnet/coreclr/issues/25882

@jkotas
Copy link
Member

jkotas commented Sep 24, 2019

It may be also interesting to look at Pressure Stall Information

@jkotas jkotas transferred this issue from dotnet/coreclr Dec 13, 2019
@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added area-PAL-coreclr untriaged New issue has not been triaged by the area owner labels Dec 13, 2019
@jeffschwMSFT jeffschwMSFT removed the untriaged New issue has not been triaged by the area owner label Jan 8, 2020
@jeffschwMSFT jeffschwMSFT added this to the 5.0 milestone Jan 8, 2020
@omajid
Copy link
Member

omajid commented Apr 9, 2020

FWIW, this should have been fixed by #34334 (aside from any new features, like Pressure Stall Information, like mentioned above).

@Maoni0
Copy link
Member Author

Maoni0 commented Apr 9, 2020

thank you very much for your contribution, @omajid 👍

@omajid
Copy link
Member

omajid commented May 4, 2020

I am interested in investigating Pressure Stall Information. Any pointers on how I can get started and where the interesting hook-points for hooking that into coreclr might be?

@Maoni0
Copy link
Member Author

Maoni0 commented May 5, 2020

there was already an attempt by @lpereira but he didn't have time to finish. please feel free to take a look at that.

@janvorli janvorli modified the milestones: 5.0.0, 6.0.0 Jul 15, 2020
MichalStrehovsky added a commit to MichalStrehovsky/runtime that referenced this issue Apr 9, 2021
Filter the list of type forwarders down to the types that we're actually generating. This makes it possible to call Assembly.GetExportedTypes on things like mscorlib without getting exceptions.
@mangod9
Copy link
Member

mangod9 commented Jul 9, 2021

Since cgroupv2 support is now enabled, perhaps we should create a separate issue for Pressure Stall Information and close this?

@mangod9
Copy link
Member

mangod9 commented Jul 20, 2021

Closing since cgroup2 support is now enabled.

@mangod9 mangod9 closed this as completed Jul 20, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Aug 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants