linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org
Subject: Re: [LSF/MM TOPIC][LSF/MM,ATTEND] shared TLB, hugetln reservations
Date: Thu, 12 Jan 2017 15:07:30 +0100	[thread overview]
Message-ID: <20170112140730.GA2452@dhcp22.suse.cz> (raw)
In-Reply-To: <cad15568-221e-82b7-a387-f23567a0bc76@oracle.com>

On Tue 10-01-17 15:02:22, Mike Kravetz wrote:
[...]
> 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 think this would help a lot. Not many people are familiar with the
current implementation and resulting problems. A high level design
documentation can help to formulate issues easier and allow others to
comment.

Thanks!
-- 
Michal Hocko
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2017-01-12 14:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 23:02 Mike Kravetz
2017-01-12 14:07 ` Michal Hocko [this message]
2017-03-09  1:30 ` [LSF/MM TOPIC][LSF/MM,ATTEND] shared TLB, hugetlb reservations Mike Kravetz
2017-03-14 18:37   ` Andrea Arcangeli
2017-03-17 22:13     ` Mike Kravetz
2017-04-03 11:51   ` Michal Hocko
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=20170112140730.GA2452@dhcp22.suse.cz \
    --to=mhocko@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