From: Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org> To: lsf-pc-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Cc: Linux NFS Mailing List <linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, Linux RDMA Mailing List <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, linux-fsdevel <linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> Subject: [LSF/MM TOPIC] Remote access to pmem on storage targets Date: Mon, 25 Jan 2016 16:19:24 -0500 [thread overview] Message-ID: <06414D5A-0632-4C74-B76C-038093E8AED3@oracle.com> (raw) I'd like to propose a discussion of how to take advantage of persistent memory in network-attached storage scenarios. RDMA runs on high speed network fabrics and offloads data transfer from host CPUs. Thus it is a good match to the performance characteristics of persistent memory. Today Linux supports iSER, SRP, and NFS/RDMA on RDMA fabrics. What kind of changes are needed in the Linux I/O stack (in particular, storage targets) and in these storage protocols to get the most benefit from ultra-low latency storage? There have been recent proposals about how storage protocols and implementations might need to change (eg. Tom Talpey's SNIA proposals for changing to a push data transfer model, Sagi's proposal to utilize DAX under the NFS/RDMA server, and my proposal for a new pNFS layout to drive RDMA data transfer directly). The outcome of the discussion would be to understand what people are working on now and what is the desired architectural approach in order to determine where storage developers should be focused. This could be either a BoF or a session during the main tracks. There is sure to be a narrow segment of each track's attendees that would have interest in this topic. -- Chuck Lever -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Chuck Lever <chuck.lever@oracle.com> To: lsf-pc@lists.linux-foundation.org Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>, Linux RDMA Mailing List <linux-rdma@vger.kernel.org>, linux-fsdevel <linux-fsdevel@vger.kernel.org> Subject: [LSF/MM TOPIC] Remote access to pmem on storage targets Date: Mon, 25 Jan 2016 16:19:24 -0500 [thread overview] Message-ID: <06414D5A-0632-4C74-B76C-038093E8AED3@oracle.com> (raw) I'd like to propose a discussion of how to take advantage of persistent memory in network-attached storage scenarios. RDMA runs on high speed network fabrics and offloads data transfer from host CPUs. Thus it is a good match to the performance characteristics of persistent memory. Today Linux supports iSER, SRP, and NFS/RDMA on RDMA fabrics. What kind of changes are needed in the Linux I/O stack (in particular, storage targets) and in these storage protocols to get the most benefit from ultra-low latency storage? There have been recent proposals about how storage protocols and implementations might need to change (eg. Tom Talpey's SNIA proposals for changing to a push data transfer model, Sagi's proposal to utilize DAX under the NFS/RDMA server, and my proposal for a new pNFS layout to drive RDMA data transfer directly). The outcome of the discussion would be to understand what people are working on now and what is the desired architectural approach in order to determine where storage developers should be focused. This could be either a BoF or a session during the main tracks. There is sure to be a narrow segment of each track's attendees that would have interest in this topic. -- Chuck Lever
next reply other threads:[~2016-01-25 21:19 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-01-25 21:19 Chuck Lever [this message] 2016-01-25 21:19 ` [LSF/MM TOPIC] Remote access to pmem on storage targets Chuck Lever [not found] ` <06414D5A-0632-4C74-B76C-038093E8AED3-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org> 2016-01-26 8:25 ` [Lsf-pc] " Jan Kara 2016-01-26 8:25 ` Jan Kara 2016-01-26 15:58 ` Chuck Lever 2016-01-27 0:04 ` Dave Chinner 2016-01-27 15:55 ` Chuck Lever 2016-01-27 15:55 ` Chuck Lever 2016-01-28 21:10 ` Dave Chinner [not found] ` <F0E2108B-891C-4570-B486-7DC7C4FB59C4-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org> 2016-01-27 10:52 ` Sagi Grimberg 2016-01-27 10:52 ` Sagi Grimberg 2016-01-26 15:25 ` Atchley, Scott 2016-01-26 15:25 ` Atchley, Scott 2016-01-26 15:25 ` Atchley, Scott [not found] ` <5FD20017-B588-42E6-BBDA-2AA8ABDBA42B-1Heg1YXhbW8@public.gmane.org> 2016-01-26 15:29 ` Chuck Lever 2016-01-26 15:29 ` Chuck Lever [not found] ` <D0C5C0B9-A1A2-4428-B3CA-7BBCC5BEF10D-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org> 2016-01-26 17:00 ` Christoph Hellwig 2016-01-26 17:00 ` Christoph Hellwig 2016-01-27 16:54 ` [LSF/MM TOPIC/ATTEND] RDMA passive target Boaz Harrosh [not found] ` <56A8F646.5020003-/8YdC2HfS5554TAoqtyWWQ@public.gmane.org> 2016-01-27 17:02 ` [Lsf-pc] " James Bottomley 2016-01-27 17:02 ` James Bottomley 2016-01-27 17:27 ` Sagi Grimberg [not found] ` <56A8FE10.7000309-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org> 2016-01-31 14:20 ` Boaz Harrosh 2016-01-31 14:20 ` Boaz Harrosh 2016-01-31 16:55 ` Yigal Korman [not found] ` <CACTTzNaOChdWN2eS9_kzv6HO_LVib-JVdkmeUn0LDe2eKxPEgA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2016-02-01 10:36 ` Sagi Grimberg 2016-02-01 10:36 ` Sagi Grimberg
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=06414D5A-0632-4C74-B76C-038093E8AED3@oracle.com \ --to=chuck.lever-qhclzuegtsvqt0dzr+alfa@public.gmane.org \ --cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=lsf-pc-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.