4level page tables for Linux
Quoted 5 lines
Numbers for all of them would be easy to deal with. Like this: pd1, pd2, pd3, pd4...
I'd number going toward the page, because that's
the order in which these things get walked.
On the other hand, these extensions tend to get made to the top, and it's confusing if, in a 2-level system, only pd3 and pd4 are used.
Perhaps a little-endian scheme (pd1 = pte, pt2=pmd, pd4=pgd) would be better after all.
Quoted 11 lines · On Thu, Oct 14, 2004 at 09:25:40AM -0000, [email protected] wrote:
Quoted 5 lines
Numbers for all of them would be easy to deal with. Like this: pd1, pd2, pd3, pd4...
I'd number going toward the page, because that's
the order in which these things get walked.On the other hand, these extensions tend to get made to the top, and it's confusing if, in a 2-level system, only pd3 and pd4 are used.
Perhaps a little-endian scheme (pd1 = pte, pt2=pmd, pd4=pgd) would be better after all.
I think the pd4=pgd, etc makes more sense as well. The names assigned now go from smallest scope (pte=pd1) to largest scope (pgd=pd3). Feels consistent.
Robin
Followup to: <[email protected]> By author: [email protected] In newsgroup: linux.dev.kernel
Quoted 4 lines
Quoted 4 lines
Numbers for all of them would be easy to deal with. Like this: pd1, pd2, pd3, pd4...
Quoted 8 lines
Quoted 2 lines
I'd number going toward the page, because that's
the order in which these things get walked.On the other hand, these extensions tend to get made to the top, and it's confusing if, in a 2-level system, only pd3 and pd4 are used.
Perhaps a little-endian scheme (pd1 = pte, pt2=pmd, pd4=pgd) would be better after all.
I believe so, for the same reason that littleendian actually makes more sense for numbers in the long run. It's one of those things where the "first perception" doesn't match what makes sense in the long run.
-hpa