linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Jerome Glisse <jglisse@redhat.com>,
	lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
	linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [Lsf-pc] [LSF/MM ATTEND] Un-addressable device memory and block/fs implications
Date: Wed, 18 Jan 2017 12:00:57 +0100	[thread overview]
Message-ID: <20170118110057.GA31377@quack2.suse.cz> (raw)
In-Reply-To: <87lgvgwoos.fsf@linux.vnet.ibm.com>

On Fri 16-12-16 08:44:11, Aneesh Kumar K.V wrote:
> Jerome Glisse <jglisse@redhat.com> writes:
> 
> > 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
> > block bounce helper (block/bounce.c) to handle this. I believe this is
> > worth discussing during summit see how people feels about such plan and
> > if they have better ideas.
> >
> >
> > I also like to join discussions on:
> >   - Peer-to-Peer DMAs between PCIe devices
> >   - CDM coherent device memory
> >   - PMEM
> >   - overall mm discussions
> 
> I would like to attend this discussion. I can talk about coherent device
> memory and how having HMM handle that will make it easy to have one
> interface for device driver. For Coherent device case we definitely need
> page cache migration support.

Aneesh, did you intend this as your request to attend? You posted it as a
reply to another email so it is not really clear. Note that each attend
request should be a separate email so that it does not get lost...

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

--
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>

      parent reply	other threads:[~2017-01-18 11:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13 18:15 [LSF/MM TOPIC] Un-addressable device memory and block/fs implications Jerome Glisse
2016-12-13 18:20 ` James Bottomley
2016-12-13 18:55   ` Jerome Glisse
2016-12-13 20:01     ` James Bottomley
2016-12-13 20:22       ` Jerome Glisse
2016-12-13 20:27       ` Dave Hansen
2016-12-13 20:15 ` Dave Chinner
2016-12-13 20:31   ` Jerome Glisse
2016-12-13 21:10     ` Dave Chinner
2016-12-13 21:24       ` Jerome Glisse
2016-12-13 22:08         ` Dave Hansen
2016-12-13 23:02           ` Jerome Glisse
2016-12-13 22:13         ` Dave Chinner
2016-12-13 22:55           ` Jerome Glisse
2016-12-14  0:14             ` Dave Chinner
2016-12-14  1:07               ` Jerome Glisse
2016-12-14  4:23                 ` Dave Chinner
2016-12-14 16:35                   ` Jerome Glisse
2016-12-14 11:13         ` [Lsf-pc] " Jan Kara
2016-12-14 17:15           ` Jerome Glisse
2016-12-15 16:19             ` Jan Kara
2016-12-15 19:14               ` Jerome Glisse
2016-12-16  8:14                 ` Jan Kara
2016-12-16  3:10               ` Aneesh Kumar K.V
2016-12-19  8:46                 ` Jan Kara
2016-12-19 17:00           ` Aneesh Kumar K.V
2016-12-14  3:55 ` Balbir Singh
2016-12-16  3:14 ` [LSF/MM ATTEND] " Aneesh Kumar K.V
2017-01-16 12:04   ` Anshuman Khandual
2017-01-16 23:15     ` John Hubbard
2017-01-18 11:00   ` Jan Kara [this message]

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=20170118110057.GA31377@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=jglisse@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).