From: bahadir@l4dev.org (Bahadir Balban)
To: linux-arm-kernel@lists.infradead.org
Subject: Split page tables
Date: Tue, 12 Jan 2010 21:15:08 +0200 [thread overview]
Message-ID: <4B4CCA3C.9090502@l4dev.org> (raw)
In-Reply-To: <1263288689.29654.8.camel@pc1117.cambridge.arm.com>
Catalin Marinas wrote:
> Hi Bahadir,
>
> (good to see you around :-))
>
Good to see you too, Catalin.
> You can configure a 2:2 split and if you want you can set TTBR1 to the
> kernel TTBR but I don't think you'd gain much. You only save about 2K of
> the user TTBR but since we allocate a 1 x 4K page pgd, there isn't any
> difference. Note the translation table entries for the kernel would
> contain either level 1 section entries or entries pointing to level 2
> tables which would be shared between all the pgd tables. I think the
> only gain is probably a memcpy of the kernel pgd into the user pgd
> during process creation.
>
I understand that level 2 tables are already shared on global mappings.
After taking a glance in pgtable.h, I see that there are 8-byte pgd
entries and extra linux tables to make it fit for linux requirements.
But still, it seems like instead of 16KB level1 tables per-space, a 2:2
split would need 8KB level1 table per space which results in 8KB savings
per-space. Am I missing something?
That said, with linux pte duplicates on every 2nd level table, it might
not be a significant gain. Perhaps you had done the correlation long ago
- but extra bits from tex remap and access flag is not enough to support
linux bits directly on the hardware pte?
Thanks,
--
Bahadir
next prev parent reply other threads:[~2010-01-12 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 19:59 Split page tables Bahadir Balban
2010-01-12 9:31 ` Catalin Marinas
2010-01-12 19:15 ` Bahadir Balban [this message]
2010-01-13 10:30 ` Catalin Marinas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B4CCA3C.9090502@l4dev.org \
--to=bahadir@l4dev.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.