linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Mike Rapoport <rppt@linux.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Vlastimil Babka <vbabka@suse.cz>,
	"Kirill A. Shutemov" <kirill@shutemov.name>,
	David Rientjes <rientjes@google.com>,
	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>,
	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: Mon, 21 Jan 2019 21:00:29 +0300	[thread overview]
Message-ID: <20190121180029.GA2332@uranus.lan> (raw)
In-Reply-To: <20190121102144.GP4087@dhcp22.suse.cz>

On Mon, Jan 21, 2019 at 11:21:44AM +0100, Michal Hocko wrote:
...
> > 
> > The patch from David obviously breaks CRIU, and I can't see a nice solution
> > that will work for everybody.
> > 
> > Of course we could add something like 'NH' to /proc/pid/smaps so that 'nh'
> > will work as David's userspace is expecting and 'NH' will represent the
> > state of VmFlags. This is hackish and ugly, though.
> > 
> > In any case, if David's patch is not reverted CRIU needs some way to know
> > if VMA has VM_NOHUGEPAGE set.
> 
> Hmm, there doesn't seem to be any follow up here and the patch is still
> in the mmotm tree AFAICS in mainline-urgent section. I thought it was
> clarified that the patch will break an existing userspace that relies on
> the documented semantic.
> 
> While it is unfortunate that the use case mentioned by David got broken
> we have provided a long term sustainable which is much better than
> relying on an undocumented side effect of the prctl implementation at
> the time.
> 
> So can we make a decision on this finally please?

As to me David's userspace application could use /proc/$pid/status
to fetch precise THP state. And the patch in mm queue simply breaks
others userspace thus should be reverted.

  reply	other threads:[~2019-01-21 18:00 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
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 [this message]
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=20190121180029.GA2332@uranus.lan \
    --to=gorcunov@gmail.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=avagin@gmail.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=kirill@shutemov.name \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=rientjes@google.com \
    --cc=rppt@linux.ibm.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