-
Notifications
You must be signed in to change notification settings - Fork 274
Rework Linker dispatching for cross-major nvJitLink/driver skew #1911
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
Open
cpcloud
wants to merge
4
commits into
NVIDIA:main
Choose a base branch
from
cpcloud:linker-dispatch-rework-712
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
00ca330
refactor(core): per-instance Linker backend dispatch
cpcloud fe5a7b3
fix(core): retain driver log buffers for CUlinkState lifetime
cpcloud 1572452
fix(core): retain cuLinkCreate optionValues array for CUlinkState lif…
cpcloud bd1874c
fix(core): release driver-backend buffers in Linker.close()
cpcloud File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
Its easy to miss the subtly here that reordering the fields breaks the assumptions of object lifetimes and can cause memory issues. Since I don't have any better ideas on how to guard against this... I'd make it VERY obvious that people should not be reordering the members here unless they know what they are doing. Something to the effect...
# WARNING: Here be dragons... do not reorder data members... <reasons>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.
I'm not convinced this is much better... but I offer it as food for thought. We could specify the correct destruction order of the members instead in a member function and manually called that when the object is destroyed by the GC. The best I can say about this is it less subtle that we are attempting to handle complext lifetime issues.
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.
cc: @leofang @mdboom