[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190211225447.GN24692@ziepe.ca>
Date: Mon, 11 Feb 2019 15:54:47 -0700
From: Jason Gunthorpe <jgg@...pe.ca>
To: Daniel Jordan <daniel.m.jordan@...cle.com>
Cc: akpm@...ux-foundation.org, dave@...olabs.net, jack@...e.cz,
cl@...ux.com, linux-mm@...ck.org, kvm@...r.kernel.org,
kvm-ppc@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
linux-fpga@...r.kernel.org, linux-kernel@...r.kernel.org,
alex.williamson@...hat.com, paulus@...abs.org,
benh@...nel.crashing.org, mpe@...erman.id.au, hao.wu@...el.com,
atull@...nel.org, mdf@...nel.org, aik@...abs.ru
Subject: Re: [PATCH 0/5] use pinned_vm instead of locked_vm to account pinned
pages
On Mon, Feb 11, 2019 at 05:44:32PM -0500, Daniel Jordan wrote:
> Hi,
>
> This series converts users that account pinned pages with locked_vm to
> account with pinned_vm instead, pinned_vm being the correct counter to
> use. It's based on a similar patch I posted recently[0].
>
> The patches are based on rdma/for-next to build on Davidlohr Bueso's
> recent conversion of pinned_vm to an atomic64_t[1]. Seems to make some
> sense for these to be routed the same way, despite lack of rdma content?
Oy.. I'd be willing to accumulate a branch with acks to send to Linus
*separately* from RDMA to Linus, but this is very abnormal.
Better to wait a few weeks for -rc1 and send patches through the
subsystem trees.
> All five of these places, and probably some of Davidlohr's conversions,
> probably want to be collapsed into a common helper in the core mm for
> accounting pinned pages. I tried, and there are several details that
> likely need discussion, so this can be done as a follow-on.
I've wondered the same..
Jason
Powered by blists - more mailing lists