[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200114124523.GM20978@mellanox.com>
Date: Tue, 14 Jan 2020 12:45:26 +0000
From: Jason Gunthorpe <jgg@...lanox.com>
To: Ralph Campbell <rcampbell@...dia.com>
CC: "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-kselftest@...r.kernel.org" <linux-kselftest@...r.kernel.org>,
Jerome Glisse <jglisse@...hat.com>,
John Hubbard <jhubbard@...dia.com>,
Christoph Hellwig <hch@....de>,
Andrew Morton <akpm@...ux-foundation.org>,
Shuah Khan <shuah@...nel.org>
Subject: Re: [PATCH v5 1/2] mm/mmu_notifier: make interval notifier updates
safe
On Mon, Jan 13, 2020 at 02:44:52PM -0800, Ralph Campbell wrote:
> I'm using the device driver lock to serialize find/insert/update/remove
> changes to the interval tree.
The device driver lock can't really fully serialize this as it doesn't
effect how the intersection lookup runs.
Jason
Powered by blists - more mailing lists