On Thu, 5 Apr 2007, Luck, Tony wrote:
> > This implements granule page sized vmemmap support for IA64.
>
> Christoph,
>
> Your calculations here are all based on a granule size of 16M, but
> it is possible to configure 64M granules.
Hmm.. Maybe we need to have a separate size for the
On Thu, 5 Apr 2007, Luck, Tony wrote:
This implements granule page sized vmemmap support for IA64.
Christoph,
Your calculations here are all based on a granule size of 16M, but
it is possible to configure 64M granules.
Hmm.. Maybe we need to have a separate size for the vmemmap
From: "Luck, Tony" <[EMAIL PROTECTED]>
Date: Thu, 5 Apr 2007 15:50:02 -0700
> Maybe a granule is not the right unit of allocation ... perhaps 4M
> would work better (4M/56 ~= 75000 pages ~= 1.1G)? But if this is
> too small, then a hard-coded 16M would be better than a granule,
> because 64M is
> This implements granule page sized vmemmap support for IA64.
Christoph,
Your calculations here are all based on a granule size of 16M, but
it is possible to configure 64M granules.
With current sizeof(struct page) == 56, a 16M page will hold enough
page structures for about 4.5G of physical
This implements granule page sized vmemmap support for IA64.
Christoph,
Your calculations here are all based on a granule size of 16M, but
it is possible to configure 64M granules.
With current sizeof(struct page) == 56, a 16M page will hold enough
page structures for about 4.5G of physical
From: Luck, Tony [EMAIL PROTECTED]
Date: Thu, 5 Apr 2007 15:50:02 -0700
Maybe a granule is not the right unit of allocation ... perhaps 4M
would work better (4M/56 ~= 75000 pages ~= 1.1G)? But if this is
too small, then a hard-coded 16M would be better than a granule,
because 64M is (IMHO)
6 matches
Mail list logo
