-
Notifications
You must be signed in to change notification settings - Fork 28
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
Add Coarse provider #715
Merged
Merged
Add Coarse provider #715
Conversation
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
ldorau
force-pushed
the
new_coarse_provider
branch
from
September 9, 2024 10:37
f6cd2b5
to
f8329d7
Compare
bratpiorka
requested changes
Sep 9, 2024
ldorau
force-pushed
the
new_coarse_provider
branch
7 times, most recently
from
September 10, 2024 08:14
c449180
to
9f24a85
Compare
ldorau
force-pushed
the
new_coarse_provider
branch
2 times, most recently
from
September 10, 2024 16:04
aadf63e
to
8ca2486
Compare
3 tasks
ldorau
force-pushed
the
new_coarse_provider
branch
4 times, most recently
from
September 16, 2024 10:02
7e98dcb
to
c832101
Compare
lplewa
reviewed
Sep 16, 2024
ldorau
force-pushed
the
new_coarse_provider
branch
9 times, most recently
from
September 18, 2024 13:55
46e2b90
to
9f61dc2
Compare
lplewa
reviewed
Oct 2, 2024
ldorau
force-pushed
the
new_coarse_provider
branch
from
October 2, 2024 14:23
589991c
to
0e32415
Compare
@lplewa Done |
@lplewa ALL issues fixed - please re-review :-) |
ldorau
force-pushed
the
new_coarse_provider
branch
7 times, most recently
from
October 3, 2024 14:03
8334765
to
1025a84
Compare
lplewa
requested changes
Oct 3, 2024
ldorau
force-pushed
the
new_coarse_provider
branch
3 times, most recently
from
October 4, 2024 12:21
ffb06cd
to
7adceea
Compare
All issues fixed, please resolve them and do not submit new ones ;-) - at least before the weekend ;-) and the best way to do that is just to merge it ;-) |
ldorau
force-pushed
the
new_coarse_provider
branch
from
October 4, 2024 12:33
7adceea
to
85e9d78
Compare
Code freeze, only critical issues will be fixed ;-) |
lplewa
approved these changes
Oct 4, 2024
Add Coarse provider - a memory provider that can manage a memory (i.e. handle the alloc() and free() ops) of a given pre-allocated buffer or of an additional upstream provider (e.g. OS Memory Provider or providers that do not support the free() operation, like the file memory provider and the DevDax memory provider). Co-developed-by: Rafał Rudnicki <[email protected]> Co-developed-by: Lukasz Dorau <[email protected]> Signed-off-by: Lukasz Dorau <[email protected]>
ldorau
force-pushed
the
new_coarse_provider
branch
from
October 5, 2024 09:44
85e9d78
to
84e7b71
Compare
@lplewa @lukaszstolarczuk All issues fixed, please resolve them all. |
bratpiorka
approved these changes
Oct 5, 2024
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.
Description
A memory provider that can provide memory from:
like the File memory provider or the DevDax memory provider - see below).
This is a continuation of #378
Checklist