common: 2.1.3-rc1 release #31
Closed
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
janekmi
approved these changes
Jan 13, 2026
Contributor
janekmi
left a comment
janekmi
left a comment
There was a problem hiding this comment.
@janekmi reviewed 49 files and all commit messages, and made 2 comments.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on @grom72).
src/test/pmempool_sync/TEST32 line 38 at r1 (raw file):
expect_normal_exit "$OBJ_VERIFY$EXESUFFIX $POOLSET pmempool$SUFFIX c v &>> $LOG" turn_on_checking_bad_blocks $POOLSET
This line should be removed from all tests which transitioned from require_fs_type non-pmem to require_real_pmem. Can we make sure it happens just after this PMDK release?
grom72
approved these changes
Jan 13, 2026
Signed-off-by: Oksana Salyk <[email protected]>
Signed-off-by: Oksana Salyk <[email protected]>
Signed-off-by: Oksana Salyk <[email protected]>
Signed-off-by: Oksana Salyk <[email protected]>
Signed-off-by: Oksana Salyk <[email protected]>
... chunk reinit Issue Huge memory blocks with the header chunk of type CHUNK_TYPE_FREE had not reinitialized their footer chunk. Context - Allocator divides the available space into zones and zones into smaller chunks. - All chunk headers belonging to a single zone are stored in an array. - Chunk header describes its: type, size_idx and flags. - Chunk can be of a few types. The types important for this patch are: CHUNK_TYPE_FOOTER, CHUNK_TYPE_FREE, and CHUNK_TYPE_USED. - CHUNK_TYPE_FREE and _USED are chunk types marking the beginning of so called huge memory block. This means this chunk and a number of chunks following it (size_idx) constitues a single allocation or a free memory. - The last chunk belonging to a huge memory block ought to be of type CHUNK_TYPE_FOOTER. Its size_idx allows to easily find the first chunk belonging to this huge memory block and determine the huge memory block type. - Huge memory blocks' footers are written immediately but persited lazily. It is not a problem at runtime since the footers are there at runtime. But in case of a crash the footers may be not persisted properly and missing on open. So, when the allocator is booted up it recreates footers just in case any of them is missing. Note: The huge memory block's first chunk header and the last chunk header (footer) are not written nor persisted in any way transactionally. The first chunk header occupies only 8 bytes so it is written and persisted atomically. But its footer is written independently and not explicitly persisted. Note: The first chunk header contains all the required info to recreate footer. The last chunk header is there only to make huge memory blocks coalescing easier to compute. Reading the footer allows to immediately find the memory block leaving just before the memory block which neighbours one might want to find. This patch makes sure the huge memory block's footer is recreated no matter whather its type is CHUNK_TYPE_FREE or CHUNK_TYPE_USED. The patch is inspired by work done for DAOS' DAV allocator (DAOS-18195) which is heavily based on the PMEMOBJ allocator. Signed-off-by: Jan Michalski <[email protected]> Inspired-by: Sherin T George <[email protected]>
Signed-off-by: Oksana Salyk <[email protected]>
Signed-off-by: liuxiang <[email protected]>
Signed-off-by: Oksana Salyk <[email protected]> Co-authored-by: Jan Michalski <[email protected]>
DAOS-18296 Signed-off-by: Jan Michalski <[email protected]>
Signed-off-by: Oksana Salyk <[email protected]>
Signed-off-by: Oksana Salyk <[email protected]>
Contributor
Author
|
I can't fix this story. |
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.
This change is