From: Jason Gunthorpe <jgg@ziepe.ca>
To: Jerome Glisse <jglisse@redhat.com>
Cc: 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 19:52:20 -0300 [thread overview]
Message-ID: <20190522225220.GC15389@ziepe.ca> (raw)
In-Reply-To: <20190522224211.GF20179@redhat.com>
On Wed, May 22, 2019 at 06:42:11PM -0400, Jerome Glisse wrote:
> > > The way race is avoided is because mm->hmm will either be NULL or
> > > point to another hmm struct before an existing hmm is free.
> >
> > There is no locking on mm->hmm so it is useless to prevent races.
>
> There is locking on mm->hmm
Not in mm_get_hmm()
> > So we agree this patch is necessary? Can you test it an ack it please?
>
> A slightly different patch than this one is necessary i will work on
> it tomorrow.
I think if you want something different you should give feedback on
this patch. You haven't rasied any defects with it.
Jason
next prev parent reply other threads:[~2019-05-22 22:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190411181314.19465-1-jglisse@redhat.com>
[not found] ` <20190506195657.GA30261@ziepe.ca>
[not found] ` <20190521205321.GC3331@redhat.com>
[not found] ` <20190522005225.GA30819@ziepe.ca>
[not found] ` <20190522174852.GA23038@redhat.com>
2019-05-22 19:22 ` [PATCH v4 0/1] Use HMM for ODP v4 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 21:12 ` Ralph Campbell
2019-05-22 22:06 ` Jerome Glisse
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 [this message]
[not found] ` <20190522235737.GD15389@ziepe.ca>
[not found] ` <20190523150432.GA5104@redhat.com>
[not found] ` <20190523154149.GB12159@ziepe.ca>
[not found] ` <20190523155207.GC5104@redhat.com>
[not found] ` <20190523163429.GC12159@ziepe.ca>
[not found] ` <20190523173302.GD5104@redhat.com>
[not found] ` <20190523175546.GE12159@ziepe.ca>
[not found] ` <20190523182458.GA3571@redhat.com>
[not found] ` <20190523191038.GG12159@ziepe.ca>
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-27 19:12 ` Jason Gunthorpe
2019-06-06 15:25 ` Jason Gunthorpe
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=20190522225220.GC15389@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=artemyko@mellanox.com \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=jglisse@redhat.com \
--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 \
/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).