GC Documentation: Update knobs doc to clarify usage#27566
GC Documentation: Update knobs doc to clarify usage#27566NickCraver wants to merge 1 commit intodotnet:masterfrom
Conversation
The current docs are a bit confusing between global and per-heap. This clarifies that and aligns the GC bits between clrconfigvalues.h and clr-configuration-knobs.md (intended to be generated, but not actually matching at the moment).
|
I would be completely ok not having this process of generating the .md from the header - for anyone who is interested in this doc it's the same amount of work to read the header so I dunno what value this generating process adds. and we get into this problem of the doc being out of sync from the header 'cause whatever that does the generation wasn't run. also it'd be nice to have one place that describes which version(s) each config is available in instead of having to look at the generated .md for each version. |
|
Related discussion: #25657 (comment) |
|
there's also #12959 in doc repo. we should just get rid of the doc in our repo and work on it there perhaps? @mariaw, where do you view the files being changed in that doc PR? |
|
Thank you for your contribution. As announced in dotnet/coreclr#27549 this repository will be moving to dotnet/runtime on November 13. If you would like to continue working on this PR after this date, the easiest way to move the change to dotnet/runtime is:
|
|
Hi @NickCraver, would mind updating your PR to change only the clrconfigvalues.h file and I'll merge it? |
|
Thank you for your contribution. As announced in #27549 the dotnet/runtime repository will be used going forward for changes to this code base. Closing this PR as no more changes will be accepted into master for this repository. If you’d like to continue working on this change please move it to dotnet/runtime. |
The current docs are a bit confusing between global and per-heap. This clarifies that and aligns the GC bits between
clrconfigvalues.handclr-configuration-knobs.md(intended to be generated, but not actually matching at the moment).In doing this and running the generation, I noticed there's a large gap between current code and what-would-be-generated documentation. Here's that current diff:
I bet this is a combination of editing the file directly (things would get lost) and not editing the file at all (new additions in the diff). I think it requires a bit of digging on if the removed items should actually be removed vs. were not added in the script-friendly way to
clrconfigvalues.h.In the TOC, note that
[ARM Configuration Knobs](#arm-configuration-knobs)actually doesn't exist...it's a dead link today. Anyway, just discovery while doing this - is cleanup wanted there or is the generation model intended to be abandoned?cc @Maoni0 @richlander