On 4/25/19 12:04 PM, rcampb...@nvidia.com wrote:
> From: Ralph Campbell
>
> Some minor wording changes and typo corrections.
>
> Signed-off-by: Ralph Campbell
> Cc: Jonathan Corbet
> Cc: Mike Rapoport
> Cc: Mike Kravetz
hugetlbfs_reserv.rst changes,
Acked-by: M
allocator.
I really do not think hugetlbfs overcommit will provide any benefit over
THP for your use case. Also, new user space code is required to "fall back"
to normal pages in the case of hugetlbfs page allocation failure. This
is not needed in the THP case.
--
Mike Kravetz
--
To
ages are not accounted for when
they are allocated as 'reserves'. It is not until these reserves are actually
used that accounting limits are checked. This 'seems' to align with general
allocation of huge pages within the pool. No accounting is done until they
are actually allocated to
On 05/17/2018 09:27 PM, TSUKADA Koutaro wrote:
> Thanks to Mike Kravetz for comment on the previous version patch.
>
> The purpose of this patch-set is to make it possible to control whether or
> not to charge surplus hugetlb pages obtained by overcommitting to memory
> cgroup. I
On 02/13/2018 05:00 PM, David Rientjes wrote:
> Specify that movablecore= can use a percent value.
>
> Remove comment about hugetlb pages not being movable per Mike.
>
> Cc: Mike Kravetz
> Signed-off-by: David Rientjes
Thanks! FWIW,
Reviewed-by: Mike Kravetz
And, that is
quot; are
> exclusive,
> - so you can NOT specify nn[KMGTPE] and "mirror" at the
> same
> - time.
> + for Movable pages. "nn[KMGTPE]", "nn%", and "mirror"
> +
Adding a brief overview of hugetlbfs reservation design and implementation
as an aid to those making code modifications in this area.
Signed-off-by: Mike Kravetz
---
Documentation/vm/00-INDEX | 2 +
Documentation/vm/hugetlbfs_reserv.txt | 529 ++
2
