From: Jerome Glisse <jglisse@redhat.com>
To: Ralph Campbell <rcampbell@nvidia.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, Leon Romanovsky <leonro@mellanox.com>,
Doug Ledford <dledford@redhat.com>,
Artemy Kovalyov <artemyko@mellanox.com>,
Moni Shoua <monis@mellanox.com>,
Mike Marciniszyn <mike.marciniszyn@intel.com>,
Kaike Wan <kaike.wan@intel.com>,
Dennis Dalessandro <dennis.dalessandro@intel.com>
Subject: Re: [PATCH v4 0/1] Use HMM for ODP v4
Date: Wed, 22 May 2019 18:06:49 -0400 [thread overview]
Message-ID: <20190522220649.GC20179@redhat.com> (raw)
In-Reply-To: <05e7f491-b8a4-4214-ab75-9ecf1128aaa6@nvidia.com>
On Wed, May 22, 2019 at 02:12:31PM -0700, Ralph Campbell wrote:
>
> On 5/22/19 1:12 PM, Jason Gunthorpe wrote:
> > On Wed, May 22, 2019 at 01:48:52PM -0400, Jerome Glisse wrote:
> >
> > > static void put_per_mm(struct ib_umem_odp *umem_odp)
> > > {
> > > struct ib_ucontext_per_mm *per_mm = umem_odp->per_mm;
> > > @@ -325,9 +283,10 @@ static void put_per_mm(struct ib_umem_odp *umem_odp)
> > > up_write(&per_mm->umem_rwsem);
> > > WARN_ON(!RB_EMPTY_ROOT(&per_mm->umem_tree.rb_root));
> > > - mmu_notifier_unregister_no_release(&per_mm->mn, per_mm->mm);
> > > + hmm_mirror_unregister(&per_mm->mirror);
> > > put_pid(per_mm->tgid);
> > > - mmu_notifier_call_srcu(&per_mm->rcu, free_per_mm);
> > > +
> > > + kfree(per_mm);
> >
> > Notice that mmu_notifier only uses SRCU to fence in-progress ops
> > callbacks, so I think hmm internally has the bug that this ODP
> > approach prevents.
> >
> > hmm should follow the same pattern ODP has and 'kfree_srcu' the hmm
> > struct, use container_of in the mmu_notifier callbacks, and use the
> > otherwise vestigal kref_get_unless_zero() to bail:
>
> You might also want to look at my patch where
> I try to fix some of these same issues (5/5).
>
> https://marc.info/?l=linux-mm&m=155718572908765&w=2
I need to review the patchset but i do not want to invert referencing
ie having mm hold reference on hmm. Will review tommorrow. I wanted to
do that today but did not had time.
next prev parent reply other threads:[~2019-05-22 22:06 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 18:13 [PATCH v4 0/1] Use HMM for ODP v4 jglisse
2019-04-11 18:13 ` [PATCH v4 1/1] RDMA/odp: convert to use " jglisse
2019-05-06 19:56 ` [PATCH v4 0/1] Use " Jason Gunthorpe
2019-05-21 20:53 ` Jerome Glisse
2019-05-21 20:53 ` Jerome Glisse
2019-05-22 0:52 ` Jason Gunthorpe
2019-05-22 17:48 ` Jerome Glisse
2019-05-22 17:48 ` Jerome Glisse
2019-05-22 18:32 ` Jason Gunthorpe
2019-05-22 19:22 ` Jason Gunthorpe
2019-05-22 21:49 ` Jerome Glisse
2019-05-22 22:43 ` Jason Gunthorpe
2019-05-22 20:12 ` Jason Gunthorpe
2019-05-22 20:12 ` Jason Gunthorpe
2019-05-22 21:12 ` Ralph Campbell
2019-05-22 21:12 ` Ralph Campbell
2019-05-22 22:06 ` Jerome Glisse [this message]
2019-05-22 22:04 ` Jerome Glisse
2019-05-22 22:39 ` Jason Gunthorpe
2019-05-22 22:42 ` Jerome Glisse
2019-05-22 22:52 ` Jason Gunthorpe
2019-05-22 23:57 ` Jason Gunthorpe
2019-05-23 15:04 ` Jerome Glisse
2019-05-23 15:41 ` Jason Gunthorpe
2019-05-23 15:52 ` Jerome Glisse
2019-05-23 16:34 ` Jason Gunthorpe
2019-05-23 17:33 ` Jerome Glisse
2019-05-23 17:55 ` Jason Gunthorpe
2019-05-23 18:24 ` Jerome Glisse
2019-05-23 19:10 ` Jason Gunthorpe
2019-05-23 19:39 ` Jerome Glisse
2019-05-23 19:47 ` Jason Gunthorpe
2019-05-24 6:40 ` Christoph Hellwig
2019-05-24 12:44 ` RFC: Run a dedicated hmm.git for 5.3 Jason Gunthorpe
2019-05-24 16:27 ` Daniel Vetter
2019-05-24 16:53 ` Jason Gunthorpe
2019-05-24 16:59 ` Daniel Vetter
2019-05-25 22:52 ` Andrew Morton
2019-05-25 22:52 ` Andrew Morton
2019-05-27 19:12 ` Jason Gunthorpe
2019-06-06 15:25 ` Jason Gunthorpe
2019-06-06 19:53 ` Stephen Rothwell
2019-06-06 19:53 ` Stephen Rothwell
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=20190522220649.GC20179@redhat.com \
--to=jglisse@redhat.com \
--cc=artemyko@mellanox.com \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kaike.wan@intel.com \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@intel.com \
--cc=monis@mellanox.com \
--cc=rcampbell@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.