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
nautilus: librbd: new "write_zeroes" API methods to supplement the "discard" APIs #36250
Conversation
Unlike the existing 'discard' option which is more of a hint to attempt to release space, the new 'write_zeroes' APIs will ensure that the entire provided extent is fully zeroed. Signed-off-by: Jason Dillaman <dillaman@redhat.com> (cherry picked from commit ae6dd86) Conflicts: src/librbd/api/Io.h/cc: logic exists in ImageRequestWQ files src/librbd/librbd.cc: trivial resolution due missing api::Io src/test/librbd/test_librbd.cc: trivial resolution (cherry picked from commit 0e3add9) Conflicts: src/librbd/io/ImageRequestWQ.cc: different locks and no overlap guard src/test/librbd/test_librbd.cc: trivial resolution
Fixes: https://tracker.ceph.com/issues/45986 Signed-off-by: Jason Dillaman <dillaman@redhat.com> (cherry picked from commit f319ecf) (cherry picked from commit f53e43c)
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.
LGTM
Yup and yup. I’ve always found it easier to not start over with a cherry-pick and instead base it on the previous release’s effort. |
discard
APIs
Oops. Nautilus PR got merged before the Octopus one from which it was cherry-picked :-( Next time I'll try to remember to add DNM. I also tend to cherry-pick from the newer stable branch if it makes the conflict resolution easier. |
So, apparently this broke the i386 build? See #36620 |
https://tracker.ceph.com/issues/46673