From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot0-f198.google.com (mail-ot0-f198.google.com [74.125.82.198]) by kanga.kvack.org (Postfix) with ESMTP id 0928A280263 for ; Tue, 16 Jan 2018 20:59:51 -0500 (EST) Received: by mail-ot0-f198.google.com with SMTP id n10so3887949otb.2 for ; Tue, 16 Jan 2018 17:59:51 -0800 (PST) Received: from mail-sor-f41.google.com (mail-sor-f41.google.com. [209.85.220.41]) by mx.google.com with SMTPS id u37sor1475116otf.202.2018.01.16.17.59.50 for (Google Transport Security); Tue, 16 Jan 2018 17:59:50 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <97e9fc59-0fc9-2c53-2713-6195f0375afe@huawei.com> References: <20180116213008.GC8801@redhat.com> <97e9fc59-0fc9-2c53-2713-6195f0375afe@huawei.com> From: "Figo.zhang" Date: Wed, 17 Jan 2018 09:59:49 +0800 Message-ID: Subject: Re: [LSF/MM TOPIC] HMM status upstream user what's next, mmu_notifier Content-Type: multipart/alternative; boundary="001a113d1a1cd84b440562ef3324" Sender: owner-linux-mm@kvack.org List-ID: To: "Liubo(OS Lab)" Cc: Jerome Glisse , lsf-pc@lists.linux-foundation.org, Linux MM , Anshuman Khandual , Balbir Singh , David Rientjes , John Hubbard , Michal Hocko --001a113d1a1cd84b440562ef3324 Content-Type: text/plain; charset="UTF-8" 2018-01-17 9:19 GMT+08:00 Liubo(OS Lab) : > On 2018/1/17 5:30, Jerome Glisse wrote: > > I want to talk about status of HMM and respective upstream user for > > it and also talk about what's next in term of features/improvement > > plan (generic page write protection, mmu_notifier, ...). Most likely > > I don't think we should consider to push more code to upstream for a > nobody-use feature. > > AFAIR, Michal also mentioned that HMM need a real user/driver before > upstream. > But I haven't seen a workable user/driver version. > > Looks like HMM is a custom framework for Nvidia, and Nvidia would not like > to open source its driver. > Even if nvidia really use HMM and open sourced its driver, it's probably > the only user. > But the HMM framework touched too much core mm code. > HMM looks suitable for FPGA user case, FPGA and CPU need coherency. ~_~ > > Cheers, > Liubo > > > short 15-30minutes if mmu_notifier is split into its own topic. > > > > I want to talk about mmu_notifier, specificaly adding more context > > information to mmu_notifier callback (why a notification is happening > > reclaim, munmap, migrate, ...). Maybe we can grow this into its own > > topic and talk about mmu_notifier and issue with it like OOM or being > > able to sleep/take lock ... and improving mitigation. > > > > People (mmu_notifier probably interest a larger set): > > "Anshuman Khandual" > > "Balbir Singh" > > "David Rientjes" > > "John Hubbard" > > "Michal Hocko" > > > > > -- > To unsubscribe, send a message with 'unsubscribe linux-mm' in > the body to majordomo@kvack.org. For more info on Linux MM, > see: http://www.linux-mm.org/ . > Don't email: email@kvack.org > --001a113d1a1cd84b440562ef3324 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


2018-01-17 9:19 GMT+08:00 Liubo(OS Lab) <liubo95@huawei.com>= :
On 2018/1/17 5:= 30, Jerome Glisse wrote:
> I want to talk about status of HMM and respective upstream user for > it and also talk about what's next in term of features/improvement=
> plan (generic page write protection, mmu_notifier, ...). Most likely
I don't think we should consider to push more code to upstream f= or a nobody-use feature.

AFAIR, Michal also mentioned that HMM need a real user/driver before upstre= am.
But I haven't seen a workable user/driver version.

Looks like HMM is a custom framework for Nvidia, and Nvidia would not like = to open source its driver.
Even if nvidia really use HMM and open sourced its driver, it's probabl= y the only user.
But the HMM framework touched too much core mm code.
= =C2=A0
HMM=C2=A0looks suitable=C2=A0for FPGA=C2=A0user case, FPGA= and CPU need coherency. ~_~
=C2=A0

Cheers,
Liubo

> short 15-30minutes if mmu_notifier is split into its own topic.
>
> I want to talk about mmu_notifier, specificaly adding more context
> information to mmu_notifier callback (why a notification is happening<= br> > reclaim, munmap, migrate, ...). Maybe we can grow this into its own > topic and talk about mmu_notifier and issue with it like OOM or being<= br> > able to sleep/take lock ... and improving mitigation.
>
> People (mmu_notifier probably interest a larger set):
>=C2=A0 =C2=A0 =C2=A0"Anshuman Khandual" <khandual@linux.vnet.ibm.com>
>=C2=A0 =C2=A0 =C2=A0"Balbir Singh" <bsingharora@gmail.com>
>=C2=A0 =C2=A0 =C2=A0"David Rientjes" <rientjes@google.com>
>=C2=A0 =C2=A0 =C2=A0"John Hubbard" <jhubbard@nvidia.com>
>=C2=A0 =C2=A0 =C2=A0"Michal Hocko" <mhocko@suse.com>
>


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.= =C2=A0 For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=3Dmailto:"dont@kvack.org"> email@kva= ck.org </a>

--001a113d1a1cd84b440562ef3324-- -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org