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

Add support for huge pages in frame allocator types #1064

Closed

Conversation

kevinaboos
Copy link
Member

No description provided.

kevinaboos added a commit that referenced this pull request Nov 8, 2023
* This is another step towards huge pages support.
  * The next step is to parameterize `AllocatedPages` too,
    and then support varying `PageSize`s within `MappedPages`.
  * Then, we will add simple routines to convert a 4K-sized
    `AllocatedPages`/`Frames` into 2M or 1G sized chunks,
    which keeps the allocation routines simpler because they only
    have to deal with 4k-sized chunks of pages or frames.

* This design enables only the `mapper` module and the
  related implementation of `MappedPages` to contain most of the
  complexity around handling multiple page sizes.
  * This is a better design choice than #1064, which attempts to
    contain that complexity within `AllocatedPages`/`Frames`,
    because that design still requires complexity within `mapper`.
@kevinaboos
Copy link
Member Author

Superseded by #1070.

@kevinaboos kevinaboos closed this Nov 8, 2023
github-actions bot pushed a commit that referenced this pull request Nov 8, 2023
* This is another step towards huge pages support.
  * The next step is to parameterize `AllocatedPages` too,
    and then support varying `PageSize`s within `MappedPages`.
  * Then, we will add simple routines to convert a 4K-sized
    `AllocatedPages`/`Frames` into 2M or 1G sized chunks,
    which keeps the allocation routines simpler because they only
    have to deal with 4k-sized chunks of pages or frames.

* This design enables only the `mapper` module and the
  related implementation of `MappedPages` to contain most of the
  complexity around handling multiple page sizes.
  * This is a better design choice than #1064, which attempts to
    contain that complexity within `AllocatedPages`/`Frames`,
    because that design still requires complexity within `mapper`. 8883597
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