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] mm patches review bandwidth
Date: Fri, 6 Jan 2017 09:08:40 +0100	[thread overview]
Message-ID: <20170106080839.GA5556@dhcp22.suse.cz> (raw)
In-Reply-To: <b1a870cc-608f-7613-c29f-9eb2a3518f8f@oracle.com>

On Thu 05-01-17 17:43:38, Mike Kravetz wrote:
> On 01/05/2017 07:37 AM, Michal Hocko wrote:
[...]
> > Another problem, somehow related, is that there are areas which have
> > evolved into a really bad shape because nobody has really payed
> > attention to them from the architectural POV when they were merged. To
> > name one the memory hotplug doesn't seem very healthy, full of kludges,
> > random hacks and fixes for fixes working for a particualr usecase
> > without any longterm vision. We have allowed to (ab)use concepts like
> > ZONE_MOVABLE which are finding new users because that seems to be the
> > simplest way forward. Now we are left with fixing the code which has
> > some fundamental issues because it is used out there. Are we going to do
> > anything about those? E.g. generate a list of them, discuss how to make
> > that code healthy again and do not allow new features until we sort that
> > out?
> 
> hugetlb reservation processing seems to be one of those areas.  I certainly
> have been guilty of stretching the limits of the current code to meet the
> demands of new functionality.  It has been my desire to do some rewrite or
> rearchitecture in this area.

I think that it would be really useful to start by a throughout design
documentation of the current code before any rewrite. I believe this
will already tell us a lot of the design complexities and shortcomings
already.
-- 
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-06  8:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05 15:37 Michal Hocko
2017-01-06  1:43 ` Mike Kravetz
2017-01-06  8:08   ` Michal Hocko [this message]
2017-01-18 12:29   ` Vlastimil Babka
2017-01-06 16:05 ` Vlastimil Babka
2017-01-13 16:56 ` Yasuaki Ishimatsu

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=20170106080839.GA5556@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