Skip to content
This repository has been archived by the owner on Mar 15, 2022. It is now read-only.

Initial draft of the GC framing document #35

Merged
merged 2 commits into from
Feb 17, 2015

Conversation

AndyAyersMS
Copy link
Member

This is a first draft of a document outlining our challenges and approach to GC reporting in MSILC.

@AndyAyersMS
Copy link
Member Author

@JosephTremoulet can you take a look? It is very similar to the word doc you've seen already.

Special reporting may also be needed for this pointers in methods that have
them.
5. Ensure that there are enough safepoints along every possible dynamic
execution path to avoid long or indefinite GC pauses.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you sure this doesn't apply in conservative mode? Specifically point 5, ensuring no starvation.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like in conservative mode you ought to be able to stop the threads wherever, at least from a GC reporting standpoint, there is no difference. I suppose there might be unsafe points here and there if we have intervals where "only live via exterior pointer" holds. I'll see what the GC guys say.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll buy that; thanks for clarifying.

@JosephTremoulet
Copy link
Contributor

The rest looks good to me.

AndyAyersMS added a commit that referenced this pull request Feb 17, 2015
Initial draft of the GC framing document
@AndyAyersMS AndyAyersMS merged commit 1f973fa into dotnet:master Feb 17, 2015
@AndyAyersMS AndyAyersMS deleted the GCDoc branch February 17, 2015 19:12
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants