linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Figo.zhang" <figo1802@gmail.com>
To: "Liubo(OS Lab)" <liubo95@huawei.com>
Cc: Jerome Glisse <jglisse@redhat.com>,
	lsf-pc@lists.linux-foundation.org, Linux MM <linux-mm@kvack.org>,
	Anshuman Khandual <khandual@linux.vnet.ibm.com>,
	Balbir Singh <bsingharora@gmail.com>,
	David Rientjes <rientjes@google.com>,
	John Hubbard <jhubbard@nvidia.com>,
	Michal Hocko <mhocko@suse.com>
Subject: Re: [LSF/MM TOPIC] HMM status upstream user what's next, mmu_notifier
Date: Wed, 17 Jan 2018 09:59:49 +0800	[thread overview]
Message-ID: <CAF7GXvpKn2xH23Q61gorGMAwPzKpo-p441pa1GS=_sQ1KxD52w@mail.gmail.com> (raw)
In-Reply-To: <97e9fc59-0fc9-2c53-2713-6195f0375afe@huawei.com>

[-- Attachment #1: Type: text/plain, Size: 1874 bytes --]

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 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" <khandual@linux.vnet.ibm.com>
> >     "Balbir Singh" <bsingharora@gmail.com>
> >     "David Rientjes" <rientjes@google.com>
> >     "John Hubbard" <jhubbard@nvidia.com>
> >     "Michal Hocko" <mhocko@suse.com>
> >
>
>
> --
> 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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
>

[-- Attachment #2: Type: text/html, Size: 3103 bytes --]

  reply	other threads:[~2018-01-17  1:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-16 21:30 Jerome Glisse
2018-01-17  1:19 ` Liubo(OS Lab)
2018-01-17  1:59   ` Figo.zhang [this message]
2018-01-17  2:05   ` Jerome Glisse
2018-01-25 15:37     ` Michal Hocko
2018-01-19  5:24 ` John Hubbard
2018-01-25 15:37 ` Michal Hocko
2018-02-14  9:15   ` Balbir Singh

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='CAF7GXvpKn2xH23Q61gorGMAwPzKpo-p441pa1GS=_sQ1KxD52w@mail.gmail.com' \
    --to=figo1802@gmail.com \
    --cc=bsingharora@gmail.com \
    --cc=jglisse@redhat.com \
    --cc=jhubbard@nvidia.com \
    --cc=khandual@linux.vnet.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=liubo95@huawei.com \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=mhocko@suse.com \
    --cc=rientjes@google.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