-
Notifications
You must be signed in to change notification settings - Fork 912
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
Unify Copy-On-Write and Spilling #15436
Merged
Merged
Changes from all commits
Commits
Show all changes
30 commits
Select commit
Hold shift + click to select a range
f2bf171
clean up
madsbk 276dd80
remove redundant methods
madsbk 2413e99
impl. and use BufferOwner.__init__
madsbk 9f4b0e1
SpillableBufferOwner: use __init__
madsbk 834f6d5
remove SpillableBuffer.mark_exposed()
madsbk 68524e4
remove SpillableBuffer.exposed
madsbk 2e43f85
SpillableBuffer(ExposureTrackedBuffer)
madsbk 659e832
mark cow tests as "spilling"
madsbk c5355a5
impl. SpillableBuffer.copy
madsbk 3581579
option: allow cow and spilling at the same time
madsbk 58f7e8e
test: skip zero-copy and no-copy-on-write test whe spilling is enabled
madsbk 6018949
cleanup
madsbk f48c529
impl. set_spill_on_demand_globally
madsbk dcff299
impl. spill_on_demand_globally
madsbk 4a8b43e
cleanup
madsbk 7344f9a
impl. test_spilling_and_copy_on_write
madsbk 1e9d061
don't copy spilled data
madsbk dc715e1
test_get_rmm_memory_resource_stack is safe again
madsbk 3eaf5e3
Apply suggestions from code review
madsbk a4a3ff4
BufferOwner: forcing keyword-only
madsbk 55027fc
Merge branch 'branch-24.06' of github.com:rapidsai/cudf into cow_and_…
madsbk 504ae9a
typo
madsbk 53106ee
Merge branch 'branch-24.06' of github.com:rapidsai/cudf into cow_and_…
madsbk ac6831a
doc
madsbk 49625fa
rename _from_*_memory => from_*_memory
madsbk f4458b8
enable must of test_series_zero_copy_cow_off again
madsbk 30cd8e6
doc
madsbk 580dead
Update python/cudf/cudf/tests/test_spilling.py
madsbk 6fe2d58
more tests
madsbk 51b4b82
Merge branch 'branch-24.06' of github.com:rapidsai/cudf into cow_and_…
madsbk 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 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
This file contains 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
vyasr marked this conversation as resolved.
Show resolved
Hide resolved
|
This file contains 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.
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.
question: should we
assert isinstance(owner, BufferOwner)
here? Or is it not necessary because we implicitly require it via the_slices
attribute?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 guess, we could add
assert isinstance(owner, BufferOwner)
inBuffer.__init__
but I am not sure if that is pythonic?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.
An assertion would basically be there to protect against developer error. There's nothing unpythonic about it, that's definitely what the functionality is there for. The main question I would have is, how would we end up with something other than a BufferOwner here, and how bad would the failure mode be? Unless the assertion makes it markedly easier to debug the code it doesn't add a whole lot of value IMHO.
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 think it is arguable a little unpythonic to prevent duck-typing by using
isinstance
to force a specify type (as opposed to a general ABC/protocol type).Anyways, in this case
as_buffer()
is the only one creatingExposureTrackedBuffer
and it explicitly sets theowner
toSpillableBufferOwner | SpillableBuffer | BufferOwner
so I don't think a type error here is likely.