From: Yigal Korman <yigal@plexistor.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
linux-nvdimm@lists.01.org,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: [LSF/MM ATTEND] NVDIMM, Persistent Memory, RDMA
Date: Thu, 28 Jan 2016 13:49:06 +0200 [thread overview]
Message-ID: <CACTTzNZ1ExP2q5K9owdvFr1Ffe2dX-p5mqa_ayPt9XmXskHVQA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
Hi,
I would like to attend LSF/MM this year.
I believe I could contribute to the following discussions:
- Remote access to pmem on storage target:
http://www.spinics.net/lists/linux-rdma/msg32848.html
- Persistent Memory Error Handling:
http://www.spinics.net/lists/linux-mm/msg100560.html
- Huge Page Futures:
http://www.spinics.net/lists/linux-mm/msg100646.html
- RDMA passive target:
http://www.spinics.net/lists/linux-rdma/msg32869.html
- Block & Filesystem interface:
http://www.spinics.net/lists/linux-fsdevel/msg93552.html
I've worked on persistent memory for the last 1.5 years at Plexistor.
And been following closely the development of the NVDIMM driver, pmem,
DAX and the user-space NVML library.
I don't have many contributions [1] but I have some hands on experience
in working with various NVDIMM vendors and testing NVDIMMs.
So I hope my point of view can help with future designs.
I've also been doing some work and investigation into pmem over RDMA,
and would like to attend these discussions as well.
[1] http://www.spinics.net/lists/stable/msg110629.html
Thank you,
Yigal
[-- Attachment #2: Type: text/html, Size: 1911 bytes --]
reply other threads:[~2016-01-28 11:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CACTTzNZ1ExP2q5K9owdvFr1Ffe2dX-p5mqa_ayPt9XmXskHVQA@mail.gmail.com \
--to=yigal@plexistor.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.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