From: Omar Sandoval <osandov@osandov.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: [LSF/MM ATTEND] swap interface improvements
Date: Thu, 15 Jan 2015 22:48:12 -0800 [thread overview]
Message-ID: <20150116064812.GA7342@mew> (raw)
Hi,
I would like to attend LSF/MM to discuss future directions for the swap
subsystem. Implementing swapfile support on BTRFS exposed a number of
deficiencies in the swap-over-NFS interface which I've been working on
recently. Additional improvements tie into the kernel AIO discussion.
Christoph also expressed interest in getting rid of the old swap path in
favor of this improved interface at some point in the future, which will
surely get into a bunch of VFS and filesystem-specific issues.
Also of interest: SMR drives, BTRFS, and performance topics.
Thanks!
--
Omar
--
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>
reply other threads:[~2015-01-16 6:48 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=20150116064812.GA7342@mew \
--to=osandov@osandov.com \
--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).