From: Mina Almasry <email@example.com>
To: Mike Kravetz <firstname.lastname@example.org>
Cc: "Aneesh Kumar" <email@example.com>,
shuah <firstname.lastname@example.org>, "David Rientjes" <email@example.com>,
"Shakeel Butt" <firstname.lastname@example.org>,
"Greg Thelen" <email@example.com>,
"Andrew Morton" <firstname.lastname@example.org>,
"open list" <email@example.com>,
firstname.lastname@example.org, "Michal Koutný" <email@example.com>
Subject: Re: [PATCH v5 0/7] hugetlb_cgroup: Add hugetlb_cgroup reservation limits
Date: Mon, 23 Sep 2019 12:18:17 -0700 [thread overview]
Message-ID: <CAHS8izOj2AT4tX-+Hcb8LB2TOUKJDHScDtJ80u4M6OWpwktq0g@mail.gmail.com> (raw)
On Mon, Sep 23, 2019 at 10:47 AM Mike Kravetz <firstname.lastname@example.org> wrote:
> On 9/19/19 3:24 PM, Mina Almasry wrote:
> > Patch series implements hugetlb_cgroup reservation usage and limits, which
> > track hugetlb reservations rather than hugetlb memory faulted in. Details of
> > the approach is 1/7.
> Thanks for your continued efforts Mina.
And thanks for your reviews so far.
> One thing that has bothered me with this approach from the beginning is that
> hugetlb reservations are related to, but somewhat distinct from hugetlb
> allocations. The original (existing) huegtlb cgroup implementation does not
> take reservations into account. This is an issue you are trying to address
> by adding a cgroup support for hugetlb reservations. However, this new
> reservation cgroup ignores hugetlb allocations at fault time.
> I 'think' the whole purpose of any hugetlb cgroup is to manage the allocation
> of hugetlb pages. Both the existing cgroup code and the reservation approach
> have what I think are some serious flaws. Consider a system with 100 hugetlb
> pages available. A sysadmin, has two groups A and B and wants to limit hugetlb
> usage to 50 pages each.
> With the existing implementation, a task in group A could create a mmap of
> 100 pages in size and reserve all 100 pages. Since the pages are 'reserved',
> nobody in group B can allocate ANY huge pages. This is true even though
> no pages have been allocated in A (or B).
> With the reservation implementation, a task in group A could use MAP_NORESERVE
> and allocate all 100 pages without taking any reservations.
> As mentioned in your documentation, it would be possible to use both the
> existing (allocation) and new reservation cgroups together. Perhaps if both
> are setup for the 50/50 split things would work a little better.
> However, instead of creating a new reservation crgoup how about adding
> reservation support to the existing allocation cgroup support. One could
> even argue that a reservation is an allocation as it sets aside huge pages
> that can only be used for a specific purpose. Here is something that
> may work.
> Starting with the existing allocation cgroup.
> - When hugetlb pages are reserved, the cgroup of the task making the
> reservations is charged. Tracking for the charged cgroup is done in the
> reservation map in the same way proposed by this patch set.
> - At page fault time,
> - If a reservation already exists for that specific area do not charge the
> faulting task. No tracking in page, just the reservation map.
> - If no reservation exists, charge the group of the faulting task. Tracking
> of this information is in the page itself as implemented today.
> - When the hugetlb object is removed, compare the reservation map with any
> allocated pages. If cgroup tracking information exists in page, uncharge
> that group. Otherwise, unharge the group (if any) in the reservation map.
> One of the advantages of a separate reservation cgroup is that the existing
> code is unmodified. Combining the two provides a more complete/accurate
> solution IMO. But, it has the potential to break existing users.
> I really would like to get feedback from anyone that knows how the existing
> hugetlb cgroup controller may be used today. Comments from Aneesh would
> be very welcome to know if reservations were considered in development of the
> existing code.
FWIW, I'm aware of the interaction with NORESERVE and my thoughts are:
AFAICT, the 2 counter approach we have here is strictly superior to
the 1 upgraded counter approach. Consider these points:
- From what I can tell so far, everything you can do with the 1
counter approach, you can do with the two counter approach by setting
both limit_in_bytes and reservation_limit_in_bytes to the limit value.
That will limit both reservations and at fault allocations.
- The 2 counter approach preserves existing usage of hugetlb cgroups,
so no need to muck around with reverting the feature some time from
now because of broken users. No existing users of hugetlb cgroups need
to worry about the effect of this on their usage.
- Users that use hugetlb memory strictly through reservations can use
only reservation_limit_in_bytes and enjoy cgroup limits that never
SIGBUS the application. This is our usage for example.
- The 2 counter approach provides more info to the sysadmin. The
sysadmin knows exactly how much reserved bytes there are via
reservation_usage_in_bytes, and how much actually in use bytes there
are via usage_in_bytes. They can even detect NORESERVE usage if
usage_in_bytes > reservation_usage_in_bytes. failcnt shows failed
reservations *and* failed allocations at fault, etc. All around better
debuggability when things go wrong. I think this is particularly
troubling for the 1 upgraded counter approach. That counter's
usage_in_bytes doesn't tell you if the usage came from reservations or
allocations at fault time.
- Honestly, I think the 2 counter approach is easier to document and
understand by the userspace? 1 counter that vaguely tracks both the
reservations and usage and decides whether or not to charge at fault
time seems hard to understand what really happened after something
goes wrong. 1 counter that tracks reservations and 1 counter that
tracks actual usage seem much simpler to digest, and provide better
visibility to what the cgroup is doing as I mentioned above.
I think it may be better if I keep the 2 counter approach but
thoroughly document the interaction between the existing counters and
NORESERVE. What do you think?
FWIW, it may be prudent to consider deprecating MAP_NORESERVE, if
that's an option. I'm not sure what that benefit that provides
applications, and on the other hand it makes it hard for the kernel to
guarantee the hugetlb memory is available to the application that
requested it, and makes it harder for the cgroups to police hugetlb
usage without SIGBUSing something. But that may be a discussion for
> Mike Kravetz
next prev parent reply other threads:[~2019-09-23 19:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 22:24 [PATCH v5 0/7] hugetlb_cgroup: Add hugetlb_cgroup reservation limits Mina Almasry
2019-09-19 22:24 ` [PATCH v5 1/7] hugetlb_cgroup: Add hugetlb_cgroup reservation counter Mina Almasry
2019-09-19 22:24 ` [PATCH v5 2/7] hugetlb_cgroup: add interface for charge/uncharge hugetlb reservations Mina Almasry
2019-09-19 22:24 ` [PATCH v5 3/7] hugetlb_cgroup: add reservation accounting for private mappings Mina Almasry
2019-09-19 22:24 ` [PATCH v5 4/7] hugetlb: disable region_add file_region coalescing Mina Almasry
2019-09-27 21:44 ` Mike Kravetz
2019-09-27 22:33 ` Mina Almasry
2019-09-19 22:24 ` [PATCH v5 5/7] hugetlb_cgroup: add accounting for shared mappings Mina Almasry
2019-09-19 22:24 ` [PATCH v5 6/7] hugetlb_cgroup: Add hugetlb_cgroup reservation tests Mina Almasry
2019-09-19 22:24 ` [PATCH v5 7/7] hugetlb_cgroup: Add hugetlb_cgroup reservation docs Mina Almasry
2019-09-23 17:47 ` [PATCH v5 0/7] hugetlb_cgroup: Add hugetlb_cgroup reservation limits Mike Kravetz
2019-09-23 19:18 ` Mina Almasry [this message]
2019-09-23 21:27 ` Mike Kravetz
2019-09-24 22:42 ` Mina Almasry
2019-09-26 19:28 ` David Rientjes
2019-09-26 21:23 ` Mike Kravetz
2019-09-27 0:55 ` Mina Almasry
2019-09-27 21:59 ` Mike Kravetz
2019-09-27 22:51 ` Mina Almasry
2019-09-27 22:56 ` Mike Kravetz
2019-09-30 15:12 ` Michal Koutný
2019-10-11 19:10 ` Mina Almasry
2019-10-11 20:41 ` Mina Almasry
2019-10-14 17:33 ` Mike Kravetz
2019-10-14 18:01 ` Mina Almasry
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 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).