From: Michal Hocko <mhocko@kernel.org>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [LSF/MM TOPIC][LSF/MM,ATTEND] shared TLB, hugetlb reservations
Date: Mon, 3 Apr 2017 13:51:37 +0200 [thread overview]
Message-ID: <20170403115137.GB24668@dhcp22.suse.cz> (raw)
In-Reply-To: <e09c529d-50e7-e6f2-8054-a34f22b5835a@oracle.com>
On Wed 08-03-17 17:30:55, Mike Kravetz wrote:
> On 01/10/2017 03:02 PM, Mike Kravetz wrote:
> > Another more concrete topic is hugetlb reservations. Michal Hocko
> > proposed the topic "mm patches review bandwidth", and brought up the
> > related subject of areas in need of attention from an architectural
> > POV. I suggested that hugetlb reservations was one such area. I'm
> > guessing it was introduced to solve a rather concrete problem. However,
> > over time additional hugetlb functionality was added and the
> > capabilities of the reservation code was stretched to accommodate.
> > It would be good to step back and take a look at the design of this
> > code to determine if a rewrite/redesign is necessary. Michal suggested
> > documenting the current design/code as a first step. If people think
> > this is worth discussion at the summit, I could put together such a
> > design before the gathering.
>
> I attempted to put together a design/overview of how hugetlb reservations
> currently work. Hopefully, this will be useful.
I am still too busy to read through this carefuly and provide a useful
feedback but I believe this should go int Documentation/vm/hugetlb$foo
file. Care to send it as a patch please?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2017-04-03 11:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cad15568-221e-82b7-a387-f23567a0bc76@oracle.com>
2017-03-09 1:30 ` Mike Kravetz
2017-03-14 18:37 ` Andrea Arcangeli
2017-03-17 22:13 ` Mike Kravetz
2017-04-03 11:51 ` Michal Hocko [this message]
2017-04-03 16:24 ` Mike Kravetz
2017-04-03 16:57 ` Michal Hocko
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170403115137.GB24668@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mike.kravetz@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
all inboxes | Powered by JetHome®