From: Michal Hocko <mhocko@kernel.org>
To: Vlastimil Babka <vbabka@suse.cz>, David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
kirill.shutemov@linux.intel.com, adobriyan@gmail.com,
Linux API <linux-api@vger.kernel.org>,
Andrei Vagin <avagin@gmail.com>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Cyrill Gorcunov <gorcunov@gmail.com>,
Pavel Emelyanov <xemul@virtuozzo.com>,
Linux-MM layout <linux-mm@kvack.org>
Subject: Re: + mm-thp-always-specify-disabled-vmas-as-nh-in-smaps.patch added to -mm tree
Date: Fri, 28 Dec 2018 13:19:56 +0100 [thread overview]
Message-ID: <20181228121956.GT16738@dhcp22.suse.cz> (raw)
In-Reply-To: <00ec4644-70c2-4bd1-ec3f-b994fa0669e8@suse.cz>
On Fri 28-12-18 11:54:17, Vlastimil Babka wrote:
[...]
> Michal has a patch [2] that reports the prctl() status separately, but
> that doesn't help David's existing userspace.
This is something that is not really clear to me. I have asked several
times already and never got any reply IIRC. The code is obviously very
specific for their setup. Why is it not viable to update the code
in question now that a long term, easily backportable and properly
supported API exists?
I do understand that a lack of such an API pushes people to use whatever
sounds usable (even when undocumented) but we do have that interface
now. So what is the roadblock?
Or do we really want to make vma flags properly supported and carved in
stone interface?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-12-28 12:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.21.1812210123210.232416@chino.kir.corp.google.com>
[not found] ` <14e15543-c18b-6fa0-e107-194216ef3ada@suse.cz>
[not found] ` <20181221151256.GA6410@dhcp22.suse.cz>
[not found] ` <20181221140301.0e87b79b923ceb6d0f683749@linux-foundation.org>
[not found] ` <alpine.DEB.2.21.1812211419320.219499@chino.kir.corp.google.com>
[not found] ` <20181224080426.GC9063@dhcp22.suse.cz>
[not found] ` <alpine.DEB.2.21.1812240058060.114867@chino.kir.corp.google.com>
[not found] ` <20181224091731.GB16738@dhcp22.suse.cz>
[not found] ` <20181227111114.5tvvkddyp7cytzeb@kshutemo-mobl1>
[not found] ` <20181227213100.aeee730c1f9ec5cb11de39a3@linux-foundation.org>
[not found] ` <20181228081847.GP16738@dhcp22.suse.cz>
2018-12-28 10:54 ` Vlastimil Babka
2018-12-28 12:19 ` Michal Hocko [this message]
2018-12-28 12:35 ` Cyrill Gorcunov
2018-12-30 17:55 ` Mike Rapoport
2019-01-15 6:32 ` Mike Rapoport
2019-01-21 10:21 ` Michal Hocko
2019-01-21 18:00 ` Cyrill Gorcunov
2019-01-21 18:18 ` Michal Hocko
2019-01-21 18:24 ` Cyrill Gorcunov
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=20181228121956.GT16738@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=avagin@gmail.com \
--cc=gorcunov@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-api@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=vbabka@suse.cz \
--cc=xemul@virtuozzo.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