[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190815001319.GF11200@ziepe.ca>
Date: Wed, 14 Aug 2019 21:13:19 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: Ralph Campbell <rcampbell@...dia.com>
Cc: linux-mm@...ck.org, Andrea Arcangeli <aarcange@...hat.com>,
Christoph Hellwig <hch@....de>,
John Hubbard <jhubbard@...dia.com>,
Jérôme Glisse <jglisse@...hat.com>,
"Kuehling, Felix" <Felix.Kuehling@....com>,
Alex Deucher <alexander.deucher@....com>,
Christian König <christian.koenig@....com>,
"David (ChunMing) Zhou" <David1.Zhou@....com>,
Dimitri Sivanich <sivanich@....com>,
dri-devel@...ts.freedesktop.org, amd-gfx@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, linux-rdma@...r.kernel.org,
iommu@...ts.linux-foundation.org, intel-gfx@...ts.freedesktop.org,
Gavin Shan <shangw@...ux.vnet.ibm.com>,
Andrea Righi <andrea@...terlinux.com>,
Christoph Hellwig <hch@...radead.org>
Subject: Re: [PATCH v3 hmm 03/11] mm/mmu_notifiers: add a get/put scheme for
the registration
On Wed, Aug 14, 2019 at 02:20:31PM -0700, Ralph Campbell wrote:
>
> On 8/6/19 4:15 PM, Jason Gunthorpe wrote:
> > From: Jason Gunthorpe <jgg@...lanox.com>
> >
> > Many places in the kernel have a flow where userspace will create some
> > object and that object will need to connect to the subsystem's
> > mmu_notifier subscription for the duration of its lifetime.
> >
> > In this case the subsystem is usually tracking multiple mm_structs and it
> > is difficult to keep track of what struct mmu_notifier's have been
> > allocated for what mm's.
> >
> > Since this has been open coded in a variety of exciting ways, provide core
> > functionality to do this safely.
> >
> > This approach uses the strct mmu_notifier_ops * as a key to determine if
>
> s/strct/struct
Yes, thanks for all of this, I like having comments, but I'm a
terrible proofreader :(
Jason
Powered by blists - more mailing lists