Re: [Lsf-pc] [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

Jan Kara writes: > On Tue 13-12-16 16:24:33, Jerome Glisse wrote: >> On Wed, Dec 14, 2016 at 08:10:41AM +1100, Dave Chinner wrote: >> > On Tue, Dec 13, 2016 at 03:31:13PM -0500, Jerome Glisse wrote: >> > > On Wed, Dec 14, 2016 at 07:15:15AM +1100, Dave Chinner wrote: >> > > > On

Re: [Lsf-pc] [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Fri 16-12-16 08:40:38, Aneesh Kumar K.V wrote: > Jan Kara writes: > > > On Wed 14-12-16 12:15:14, Jerome Glisse wrote: > > > page handling> > > > >> > So won't it be easier to leave the pagecache page where it is and *copy* > >> > it > >> > to the device? Can the device notify

Re: [Lsf-pc] [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Thu 15-12-16 14:14:53, Jerome Glisse wrote: > On Thu, Dec 15, 2016 at 05:19:39PM +0100, Jan Kara wrote: > > On Wed 14-12-16 12:15:14, Jerome Glisse wrote: > > > page handling> > > > > > > So won't it be easier to leave the pagecache page where it is and > > > > *copy* it > > > > to the

Re: [Lsf-pc] [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

Jan Kara writes: > On Wed 14-12-16 12:15:14, Jerome Glisse wrote: > page handling> > >> > So won't it be easier to leave the pagecache page where it is and *copy* it >> > to the device? Can the device notify us *before* it is going to modify a >> > page, not just after it has

Re: [Lsf-pc] [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Thu, Dec 15, 2016 at 05:19:39PM +0100, Jan Kara wrote: > On Wed 14-12-16 12:15:14, Jerome Glisse wrote: > page handling> > > > > So won't it be easier to leave the pagecache page where it is and *copy* > > > it > > > to the device? Can the device notify us *before* it is going to modify a >

Re: [Lsf-pc] [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Wed 14-12-16 12:15:14, Jerome Glisse wrote: > > So won't it be easier to leave the pagecache page where it is and *copy* it > > to the device? Can the device notify us *before* it is going to modify a > > page, not just after it has modified it? Possibly if we just give it the > > page

Re: [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Wed, Dec 14, 2016 at 03:23:13PM +1100, Dave Chinner wrote: > On Tue, Dec 13, 2016 at 08:07:58PM -0500, Jerome Glisse wrote: > > On Wed, Dec 14, 2016 at 11:14:22AM +1100, Dave Chinner wrote: > > > On Tue, Dec 13, 2016 at 05:55:24PM -0500, Jerome Glisse wrote: > > > > On Wed, Dec 14, 2016 at

Re: [Lsf-pc] [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Tue 13-12-16 16:24:33, Jerome Glisse wrote: > On Wed, Dec 14, 2016 at 08:10:41AM +1100, Dave Chinner wrote: > > On Tue, Dec 13, 2016 at 03:31:13PM -0500, Jerome Glisse wrote: > > > On Wed, Dec 14, 2016 at 07:15:15AM +1100, Dave Chinner wrote: > > > > On Tue, Dec 13, 2016 at 01:15:11PM -0500,

Re: [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Tue, Dec 13, 2016 at 08:07:58PM -0500, Jerome Glisse wrote: > On Wed, Dec 14, 2016 at 11:14:22AM +1100, Dave Chinner wrote: > > On Tue, Dec 13, 2016 at 05:55:24PM -0500, Jerome Glisse wrote: > > > On Wed, Dec 14, 2016 at 09:13:22AM +1100, Dave Chinner wrote: > > > > On Tue, Dec 13, 2016 at

Re: [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Wed, Dec 14, 2016 at 5:15 AM, Jerome Glisse wrote: > I would like to discuss un-addressable device memory in the context of > filesystem and block device. Specificaly how to handle write-back, read, > ... when a filesystem page is migrated to device memory that CPU can not

Re: [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Wed, Dec 14, 2016 at 11:14:22AM +1100, Dave Chinner wrote: > On Tue, Dec 13, 2016 at 05:55:24PM -0500, Jerome Glisse wrote: > > On Wed, Dec 14, 2016 at 09:13:22AM +1100, Dave Chinner wrote: > > > On Tue, Dec 13, 2016 at 04:24:33PM -0500, Jerome Glisse wrote: > > > > On Wed, Dec 14, 2016 at

Re: [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Tue, Dec 13, 2016 at 05:55:24PM -0500, Jerome Glisse wrote: > On Wed, Dec 14, 2016 at 09:13:22AM +1100, Dave Chinner wrote: > > On Tue, Dec 13, 2016 at 04:24:33PM -0500, Jerome Glisse wrote: > > > On Wed, Dec 14, 2016 at 08:10:41AM +1100, Dave Chinner wrote: > > > > > From kernel point of view

Re: [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Tue, Dec 13, 2016 at 02:08:22PM -0800, Dave Hansen wrote: > On 12/13/2016 01:24 PM, Jerome Glisse wrote: > > > >>> > > From kernel point of view such memory is almost like any other, it > >>> > > has a struct page and most of the mm code is non the wiser, nor need > >>> > > to be about it. CPU

Re: [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Wed, Dec 14, 2016 at 09:13:22AM +1100, Dave Chinner wrote: > On Tue, Dec 13, 2016 at 04:24:33PM -0500, Jerome Glisse wrote: > > On Wed, Dec 14, 2016 at 08:10:41AM +1100, Dave Chinner wrote: > > > On Tue, Dec 13, 2016 at 03:31:13PM -0500, Jerome Glisse wrote: > > > > On Wed, Dec 14, 2016 at

Re: [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Tue, Dec 13, 2016 at 04:24:33PM -0500, Jerome Glisse wrote: > On Wed, Dec 14, 2016 at 08:10:41AM +1100, Dave Chinner wrote: > > On Tue, Dec 13, 2016 at 03:31:13PM -0500, Jerome Glisse wrote: > > > On Wed, Dec 14, 2016 at 07:15:15AM +1100, Dave Chinner wrote: > > > > On Tue, Dec 13, 2016 at

Re: [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On 12/13/2016 01:24 PM, Jerome Glisse wrote: > >>> > > From kernel point of view such memory is almost like any other, it >>> > > has a struct page and most of the mm code is non the wiser, nor need >>> > > to be about it. CPU access trigger a migration back to regular CPU >>> > > accessible

Re: [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Wed, Dec 14, 2016 at 08:10:41AM +1100, Dave Chinner wrote: > On Tue, Dec 13, 2016 at 03:31:13PM -0500, Jerome Glisse wrote: > > On Wed, Dec 14, 2016 at 07:15:15AM +1100, Dave Chinner wrote: > > > On Tue, Dec 13, 2016 at 01:15:11PM -0500, Jerome Glisse wrote: > > > > I would like to discuss

Re: [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Tue, Dec 13, 2016 at 03:31:13PM -0500, Jerome Glisse wrote: > On Wed, Dec 14, 2016 at 07:15:15AM +1100, Dave Chinner wrote: > > On Tue, Dec 13, 2016 at 01:15:11PM -0500, Jerome Glisse wrote: > > > I would like to discuss un-addressable device memory in the context of > > > filesystem and block

Re: [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Wed, Dec 14, 2016 at 07:15:15AM +1100, Dave Chinner wrote: > On Tue, Dec 13, 2016 at 01:15:11PM -0500, Jerome Glisse wrote: > > I would like to discuss un-addressable device memory in the context of > > filesystem and block device. Specificaly how to handle write-back, read, > > ... when a

Re: [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On 12/13/2016 12:01 PM, James Bottomley wrote: >> > Second aspect is that even if memory i am dealing with is un >> > -addressable i still have struct page for it and i want to be able to >> > use regular page migration. > Tmem keeps a struct page ... what's the problem with page migration? > the

Re: [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Tue, Dec 13, 2016 at 12:01:04PM -0800, James Bottomley wrote: > On Tue, 2016-12-13 at 13:55 -0500, Jerome Glisse wrote: > > On Tue, Dec 13, 2016 at 10:20:52AM -0800, James Bottomley wrote: > > > On Tue, 2016-12-13 at 13:15 -0500, Jerome Glisse wrote: > > > > I would like to discuss

Re: [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Tue, Dec 13, 2016 at 01:15:11PM -0500, Jerome Glisse wrote: > I would like to discuss un-addressable device memory in the context of > filesystem and block device. Specificaly how to handle write-back, read, > ... when a filesystem page is migrated to device memory that CPU can not > access.

Re: [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Tue, 2016-12-13 at 13:55 -0500, Jerome Glisse wrote: > On Tue, Dec 13, 2016 at 10:20:52AM -0800, James Bottomley wrote: > > On Tue, 2016-12-13 at 13:15 -0500, Jerome Glisse wrote: > > > I would like to discuss un-addressable device memory in the > > > context > > > of filesystem and block

Re: [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Tue, Dec 13, 2016 at 10:20:52AM -0800, James Bottomley wrote: > On Tue, 2016-12-13 at 13:15 -0500, Jerome Glisse wrote: > > I would like to discuss un-addressable device memory in the context > > of filesystem and block device. Specificaly how to handle write-back, > > read, ... when a

Re: [LSF/MM TOPIC] Un-addressable device memory and block/fs implications

On Tue, 2016-12-13 at 13:15 -0500, Jerome Glisse wrote: > I would like to discuss un-addressable device memory in the context > of filesystem and block device. Specificaly how to handle write-back, > read, ... when a filesystem page is migrated to device memory that > CPU can not access. > > I

[LSF/MM TOPIC] Un-addressable device memory and block/fs implications

I would like to discuss un-addressable device memory in the context of filesystem and block device. Specificaly how to handle write-back, read, ... when a filesystem page is migrated to device memory that CPU can not access. I intend to post a patchset leveraging the same idea as the existing