xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
* ARM - why does setup_frametable_size() round frametable_size to 32MB ?
@ 2015-07-17 21:19 Chris (Christopher) Brand
  2015-07-18 11:58 ` Ian Campbell
  0 siblings, 1 reply; 3+ messages in thread
From: Chris (Christopher) Brand @ 2015-07-17 21:19 UTC (permalink / raw)
  To: xen-devel@lists.xen.org

Hi,

I'm working on a platform with a mere 2GB of RAM, and trying to
trim the Xen footprint down as much as possible. I've found two
places where Xen uses more memory than it seems it needs to,
one of which is the frametable. On a 2GB system, frametable_size
is initially calculated as 16MB, but is then rounded up to 32MB.
can somebody tell me why this is done, and therefore whether
it can be avoided ? I assume it's because the code then calls
create_32mb_mappings(), in which case I guess my question
is what's special about 32MB ?

    unsigned long frametable_size = nr_pdxs * sizeof(struct page_info);
[...]
    /* Round up to 32M boundary */
    frametable_size = (frametable_size + 0x1ffffff) & ~0x1ffffff;

Thanks,

Chris

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-07-20 20:54 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-07-17 21:19 ARM - why does setup_frametable_size() round frametable_size to 32MB ? Chris (Christopher) Brand
2015-07-18 11:58 ` Ian Campbell
2015-07-20 20:54   ` Chris (Christopher) Brand

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).