From: Michal Hocko <mhocko@kernel.org>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Alexey Dobriyan <adobriyan@gmail.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-api@vger.kernel.org
Subject: Re: [RFC PATCH] mm, proc: report PR_SET_THP_DISABLE in proc
Date: Wed, 14 Nov 2018 14:23:06 +0100 [thread overview]
Message-ID: <20181114132306.GX23419@dhcp22.suse.cz> (raw)
In-Reply-To: <20181018070031.GW18839@dhcp22.suse.cz>
On Thu 18-10-18 09:00:31, Michal Hocko wrote:
> On Wed 17-10-18 12:59:18, David Rientjes wrote:
> > On Wed, 17 Oct 2018, Michal Hocko wrote:
> >
> > > Do you know of any other userspace except your usecase? Is there
> > > anything fundamental that would prevent a proper API adoption for you?
> > >
> >
> > Yes, it would require us to go back in time and build patched binaries.
>
> I read that as there is a fundamental problem to update existing
> binaries. If that is the case then there surely is no way around it
> and another sad page in the screwed up APIs book we provide.
>
> But I was under impression that the SW stack which actually does the
> monitoring is under your controll. Moreover I was under impression that
> you do not use the current vanilla kernel so there is no need for an
> immediate change on your end. It is trivial to come up with a backward
> compatible way to check for the new flag (if it is not present then
> fallback to vma flags).
>
> I am sorry for pushing here but if this is just a matter of a _single_
> user which _can_ be fixed with a reasonable effort then I would love to
> see the future api unscrewed.
ping
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-11-14 13:23 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 17:55 [patch] mm, thp: always specify ineligible vmas as nh in smaps David Rientjes
2018-09-24 18:25 ` Vlastimil Babka
2018-09-24 19:17 ` David Rientjes
2018-09-24 19:30 ` [patch v2] " David Rientjes
2018-09-24 19:56 ` Michal Hocko
2018-09-24 20:02 ` Michal Hocko
2018-09-24 20:43 ` Vlastimil Babka
2018-09-25 5:50 ` Michal Hocko
2018-09-25 19:52 ` David Rientjes
2018-09-25 20:29 ` Michal Hocko
2018-09-25 21:45 ` David Rientjes
2018-09-25 22:04 ` Andrew Morton
2018-09-26 0:55 ` David Rientjes
2018-09-26 6:06 ` Michal Hocko
2018-10-02 11:28 ` [RFC PATCH] mm, proc: report PR_SET_THP_DISABLE in proc Michal Hocko
2018-10-02 20:29 ` David Rientjes
2018-10-03 7:36 ` Michal Hocko
2018-10-03 22:51 ` David Rientjes
2018-10-04 5:58 ` Michal Hocko
2018-10-04 9:15 ` David Rientjes
2018-10-04 9:46 ` Michal Hocko
2018-10-04 18:34 ` David Rientjes
2018-10-09 8:33 ` Michal Hocko
2018-10-15 15:03 ` Michal Hocko
2018-10-15 22:25 ` David Rientjes
2018-10-16 10:48 ` Michal Hocko
2018-10-16 21:24 ` David Rientjes
2018-10-17 7:05 ` Michal Hocko
2018-10-17 19:59 ` David Rientjes
2018-10-18 7:00 ` Michal Hocko
2018-11-14 13:23 ` Michal Hocko [this message]
2018-11-14 21:41 ` David Rientjes
2018-11-15 9:02 ` Michal Hocko
2018-11-15 9:22 ` Michal Hocko
2018-11-19 22:05 ` David Rientjes
2018-11-20 7:48 ` Michal Hocko
2018-10-03 17:33 ` Mike Rapoport
2018-09-25 21:50 ` [patch v3] mm, thp: always specify disabled vmas as nh in smaps David Rientjes
2018-09-26 6:12 ` Michal Hocko
2018-09-26 7:17 ` Michal Hocko
2018-09-26 8:40 ` Vlastimil Babka
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=20181114132306.GX23419@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).