[Static Runtime] Prototype: Arena allocate StorageImpls for managed tensors #66130
Conversation
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
…ensors Prototype as mentioned in SR chat. Have to run; will clean up and fill in proper summary later. Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/) [ghstack-poisoned]
CI Flow Status⚛️ CI FlowRuleset - Version:
You can add a comment to the PR and tag @pytorchbot with the following commands: # ciflow rerun, "ciflow/default" will always be added automatically
@pytorchbot ciflow rerun
# ciflow rerun with additional labels "-l <ciflow/label_name>", which is equivalent to adding these labels manually and trigger the rerun
@pytorchbot ciflow rerun -l ciflow/scheduled -l ciflow/slowFor more information, please take a look at the CI Flow Wiki. |
🔗 Helpful links
💊 CI failures summary and remediationsAs of commit 42557cd (more details on the Dr. CI page): 💚 💚 Looks good so far! There are no failures yet. 💚 💚 This comment was automatically generated by Dr. CI (expand for details).Please report bugs/suggestions to the (internal) Dr. CI Users group. |
facebook-github-bot
added
oncall: jit
swolchok
added a commit
that referenced
this pull request
Oct 5, 2021
…ensors Prototype as mentioned in SR chat. Have to run; will clean up and fill in proper summary later. Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/) ghstack-source-id: 139698139 Pull Request resolved: #66130
…r managed tensors" We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/) [ghstack-poisoned]
swolchok
added a commit
that referenced
this pull request
Oct 5, 2021
Pull Request resolved: #66130 We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. ghstack-source-id: 139765254 Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/)
…r managed tensors" We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/) [ghstack-poisoned]
This was referenced Oct 15, 2021
swolchok
added a commit
that referenced
this pull request
Oct 15, 2021
Pull Request resolved: #66130 We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. ghstack-source-id: 140693022 Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/)
…r managed tensors" We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/) [ghstack-poisoned]
…r managed tensors" We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/) [ghstack-poisoned]
swolchok
added a commit
that referenced
this pull request
Oct 18, 2021
Pull Request resolved: #66130 We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. ghstack-source-id: 140876408 Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/)
…r managed tensors" We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/) [ghstack-poisoned]
…r managed tensors" We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/) [ghstack-poisoned]
swolchok
added a commit
that referenced
this pull request
Oct 19, 2021
Pull Request resolved: #66130 We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. ghstack-source-id: 140988867 Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/)
…r managed tensors" We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/) [ghstack-poisoned]
swolchok
added a commit
that referenced
this pull request
Oct 26, 2021
Pull Request resolved: #66130 We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. ghstack-source-id: 141595119 Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/)
…r managed tensors" We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/) [ghstack-poisoned]
swolchok
added a commit
that referenced
this pull request
Nov 1, 2021
Pull Request resolved: #66130 We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. ghstack-source-id: 142105253 Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/)
…r managed tensors" We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/) [ghstack-poisoned]
swolchok
added a commit
that referenced
this pull request
Nov 2, 2021
Pull Request resolved: #66130 We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. ghstack-source-id: 142192613 Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/)
…r managed tensors" We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/) [ghstack-poisoned]
swolchok
added a commit
that referenced
this pull request
Nov 2, 2021
Pull Request resolved: #66130 We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. ghstack-source-id: 142226109 Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/)
…r managed tensors" We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/) [ghstack-poisoned]
…r managed tensors" We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/) [ghstack-poisoned]
swolchok
added a commit
that referenced
this pull request
Nov 3, 2021
Pull Request resolved: #66130 We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. ghstack-source-id: 142354034 Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/)
…r managed tensors" We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/) [ghstack-poisoned]
swolchok
added a commit
that referenced
this pull request
Nov 4, 2021
Pull Request resolved: #66130 We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl. ghstack-source-id: 142427752 Differential Revision: [D31357486](https://our.internmc.facebook.com/intern/diff/D31357486/)
|
This pull request has been merged in b0c0529. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Stack from ghstack:
We're reusing backing storage for these tensors, which is only safe because they have non-overlapping lifetimes. Accordingly, it seems that they can also share their StorageImpl.
Differential Revision: D31357486