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

Page Table Interface Design #374

Open
hungry-foolish opened this issue Sep 13, 2018 · 0 comments
Open

Page Table Interface Design #374

hungry-foolish opened this issue Sep 13, 2018 · 0 comments
Assignees
Labels
C-baremetal For Baremetal related items C-kernel P-low System issue, but unlikely to cause immediate problems T-design T-optimization

Comments

@hungry-foolish
Copy link
Contributor

In the current page table interface design, the map operation always goes through many layers of page table to map in a single page. If we can use the intermediate layers and map pages between them, then more work can be handled by the user level, and we can spare these lookups in the kernel.

On potential problem is liveness, because we use such IDs to track the validity of components. It is still unclear whether this will influence the design of this interface.

@hungry-foolish hungry-foolish added the P-low System issue, but unlikely to cause immediate problems label Sep 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-baremetal For Baremetal related items C-kernel P-low System issue, but unlikely to cause immediate problems T-design T-optimization
Projects
None yet
Development

No branches or pull requests

2 participants