Skip to content
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

Enqueue to BlockQueue backwards #1235

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Conversation

wks
Copy link
Collaborator

@wks wks commented Nov 13, 2024

Due to the LIFO nature of BlockQueue, if we enqueue multiple blocks into BlockQueue forwards, allocation fast paths will get blocks from BlockQueue in the opposite direction. This commit fixes this anomaly by enqueuing consecutive blocks backwards.

This PR is currently a DRAFT.

  1. We modified alloc_pages_slow_sync so that blocks of a new Chunk will be enqueued backwards. We observe that in the beginning of execution, mutators obtain blocks forwards. But after one GC, mutators will start to obtain blocks backwards again. It may be related to SweepChunk work packets still sweeping blocks forwards and enqueuing blocks in the same order.
  2. Remove debugging log statements before merging.

Due to the LIFO nature of BlockQueue, if we enqueue multiple blocks into
BlockQueue forwards, allocation fast paths will get blocks from
BlockQueue in the opposite direction.  This commit fixes this anomaly by
enqueuing consecutive blocks backwards.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant