>>> On 13.10.17 at 12:44, wrote:
> On Fri, Oct 13, 2017 at 08:59:29AM +, Jan Beulich wrote:
>> >>> On 13.10.17 at 10:49, wrote:
>> On 29.09.17 at 13:25, wrote:
>> >> nr_pages doesn't take into account holes or MMIO regions, and
>> >> underestimates the amount of memory needed for paging
On Fri, Oct 13, 2017 at 08:59:29AM +, Jan Beulich wrote:
> >>> On 13.10.17 at 10:49, wrote:
> On 29.09.17 at 13:25, wrote:
> >> nr_pages doesn't take into account holes or MMIO regions, and
> >> underestimates the amount of memory needed for paging. Be on the safe
> >> side and use max_p
>>> On 13.10.17 at 10:49, wrote:
On 29.09.17 at 13:25, wrote:
>> nr_pages doesn't take into account holes or MMIO regions, and
>> underestimates the amount of memory needed for paging. Be on the safe
>> side and use max_pdx instead.
>>
>> Note that both cases are just approximations, but us
>>> On 29.09.17 at 13:25, wrote:
> nr_pages doesn't take into account holes or MMIO regions, and
> underestimates the amount of memory needed for paging. Be on the safe
> side and use max_pdx instead.
>
> Note that both cases are just approximations, but using max_pdx yields
> a number of free pa
nr_pages doesn't take into account holes or MMIO regions, and
underestimates the amount of memory needed for paging. Be on the safe
side and use max_pdx instead.
Note that both cases are just approximations, but using max_pdx yields
a number of free pages after Dom0 build always greater than the
m
