From: Dmitry Monakhov <dmonakhov@openvz.org>
To: "lsf-pc\@lists.linux-foundation.org" <lsf-pc@lists.linux-foundation.org>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
linux-fsdevel@vger.kernel.org,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: [LSF/MM ATTEND] ext4, DAX pmem/fsync
Date: Mon, 08 Feb 2016 12:00:22 +0300 [thread overview]
Message-ID: <87lh6vwp95.fsf@openvz.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
I would like to attend LSF/MM 2016 to participate in discussions around
the optimization of the block and MM for low latency NVM technologies.
Primary target of interests is to improving DAX performance for general
purpose FS.
While working on LightVM project (approach lighter that traditional VM, but more
secure that containers) we found that existing DAX infrastructure is too
far from optimum:
0) DAX msync/fsync patch-set is has a lot in TODO list
1) DAX implementation has number of significant SMP scalability issues.
I would like to attend LSF/MM this year. I believe I could contribute to the
following discussions:
* Block & Filesystem interface from Steven Whitehouse
http://www.spinics.net/lists/linux-fsdevel/msg93552.html
* Persistent memory: pmem as storage device vs pmem as memory from Dan Williams
https://lists.01.org/pipermail/linux-nvdimm/2016-February/004331.html
* Persistent Memory Error Handling from Jeff Moyer:
http://www.spinics.net/lists/linux-mm/msg100560.html
* FS block allocator modification for SMR Zoned Block Devices
* EXT4-mini sumit
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: dmonakhov@openvz.org (Dmitry Monakhov)
Subject: [LSF/MM ATTEND] ext4, DAX pmem/fsync
Date: Mon, 08 Feb 2016 12:00:22 +0300 [thread overview]
Message-ID: <87lh6vwp95.fsf@openvz.org> (raw)
I would like to attend LSF/MM 2016 to participate in discussions around
the optimization of the block and MM for low latency NVM technologies.
Primary target of interests is to improving DAX performance for general
purpose FS.
While working on LightVM project (approach lighter that traditional VM, but more
secure that containers) we found that existing DAX infrastructure is too
far from optimum:
0) DAX msync/fsync patch-set is has a lot in TODO list
1) DAX implementation has number of significant SMP scalability issues.
I would like to attend LSF/MM this year. I believe I could contribute to the
following discussions:
* Block & Filesystem interface from Steven Whitehouse
http://www.spinics.net/lists/linux-fsdevel/msg93552.html
* Persistent memory: pmem as storage device vs pmem as memory from Dan Williams
https://lists.01.org/pipermail/linux-nvdimm/2016-February/004331.html
* Persistent Memory Error Handling from Jeff Moyer:
http://www.spinics.net/lists/linux-mm/msg100560.html
* FS block allocator modification for SMR Zoned Block Devices
* EXT4-mini sumit
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 472 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20160208/74eaf1a4/attachment-0001.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Monakhov <dmonakhov@openvz.org>
To: "lsf-pc@lists.linux-foundation.org" <lsf-pc@lists.linux-foundation.org>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
linux-fsdevel@vger.kernel.org,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: [LSF/MM ATTEND] ext4, DAX pmem/fsync
Date: Mon, 08 Feb 2016 12:00:22 +0300 [thread overview]
Message-ID: <87lh6vwp95.fsf@openvz.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
I would like to attend LSF/MM 2016 to participate in discussions around
the optimization of the block and MM for low latency NVM technologies.
Primary target of interests is to improving DAX performance for general
purpose FS.
While working on LightVM project (approach lighter that traditional VM, but more
secure that containers) we found that existing DAX infrastructure is too
far from optimum:
0) DAX msync/fsync patch-set is has a lot in TODO list
1) DAX implementation has number of significant SMP scalability issues.
I would like to attend LSF/MM this year. I believe I could contribute to the
following discussions:
* Block & Filesystem interface from Steven Whitehouse
http://www.spinics.net/lists/linux-fsdevel/msg93552.html
* Persistent memory: pmem as storage device vs pmem as memory from Dan Williams
https://lists.01.org/pipermail/linux-nvdimm/2016-February/004331.html
* Persistent Memory Error Handling from Jeff Moyer:
http://www.spinics.net/lists/linux-mm/msg100560.html
* FS block allocator modification for SMR Zoned Block Devices
* EXT4-mini sumit
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next reply other threads:[~2016-02-08 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 9:00 Dmitry Monakhov [this message]
2016-02-08 9:00 ` [LSF/MM ATTEND] ext4, DAX pmem/fsync Dmitry Monakhov
2016-02-08 9:00 ` Dmitry Monakhov
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=87lh6vwp95.fsf@openvz.org \
--to=dmonakhov@openvz.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvme@lists.infradead.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 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.