Re: [HMM 00/15] HMM (Heterogeneous Memory Management) v23

2017-06-23 Thread Jerome Glisse
On Fri, Jun 23, 2017 at 11:00:37PM +0800, Bob Liu wrote: > Hi, > > On Thu, May 25, 2017 at 1:20 AM, Jérôme Glisse wrote: > > Patchset is on top of git://git.cmpxchg.org/linux-mmotm.git so i > > test same kernel as kbuild system, git branch: > > > > https://cgit.freedesktop.org/~glisse/linux/log/?

Re: [HMM 00/15] HMM (Heterogeneous Memory Management) v23

2017-06-23 Thread Bob Liu
Hi, On Thu, May 25, 2017 at 1:20 AM, Jérôme Glisse wrote: > Patchset is on top of git://git.cmpxchg.org/linux-mmotm.git so i > test same kernel as kbuild system, git branch: > > https://cgit.freedesktop.org/~glisse/linux/log/?h=hmm-v23 > > Change since v22 is use of static key for special ZONE_DE

Re: [HMM 00/15] HMM (Heterogeneous Memory Management) v23

2017-06-16 Thread Jerome Glisse
.org; linux- > >m...@kvack.org; Dan Williams; Kirill A . Shutemov; John Hubbard; Sander, Ben; > >Kuehling, Felix > >Subject: Re: [HMM 00/15] HMM (Heterogeneous Memory Management) v23 > > > >On Fri, Jun 16, 2017 at 07:22:05AM +, Bridgman, John wrote: > >> H

RE: [HMM 00/15] HMM (Heterogeneous Memory Management) v23

2017-06-16 Thread Bridgman, John
er, Ben; >Kuehling, Felix >Subject: Re: [HMM 00/15] HMM (Heterogeneous Memory Management) v23 > >On Fri, Jun 16, 2017 at 07:22:05AM +, Bridgman, John wrote: >> Hi Jerome, >> >> I'm just getting back to this; sorry for the late responses. >> >> Your descri

Re: [HMM 00/15] HMM (Heterogeneous Memory Management) v23

2017-06-16 Thread Jerome Glisse
On Fri, Jun 16, 2017 at 07:22:05AM +, Bridgman, John wrote: > Hi Jerome, > > I'm just getting back to this; sorry for the late responses. > > Your description of HMM talks about blocking CPU accesses when a page > has been migrated to device memory, and you treat that as a "given" in > the

RE: [HMM 00/15] HMM (Heterogeneous Memory Management) v23

2017-06-16 Thread Bridgman, John
Hi Jerome, I'm just getting back to this; sorry for the late responses. Your description of HMM talks about blocking CPU accesses when a page has been migrated to device memory, and you treat that as a "given" in the HMM design. Other than BAR limits, coherency between CPU and device caches a