Closed
Conversation
65a6724 to
40b58b3
Compare
40b58b3 to
d69a027
Compare
Member
Author
|
I have a trouble handling memory pool initialization (https://github.com/niboshi/chainer/blob/d69a027ddcf19c71cc386ebd0e3c88aa76d398a8/chainer/cuda.py#L132), which is currently done as module-level code. If we delay availability determination, I have no idea when they should be done. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 30 days if no further activity occurs. Thank you for your contributions. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 30 days if no further activity occurs. Thank you for your contributions. |
|
This issue is closed as announced. Feel free to re-open it if needed. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
(See: cupy/cupy#247)
Check
cupy.availablewhen settingchainer.cuda.available, so that it will beFalsewhen there is no available device (byCUDA_VISIBLE_DEVICES=-1)cupy/cupy#247 should be merged first.