linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Bates <Stephen.Bates@pmcs.com>
To: "lsf-pc@lists.linux-foundation.org" <lsf-pc@lists.linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: [LSF/MM ATTEND] blk-mq polling, nvme, pmem (for iomem) and non-block based SSDs.
Date: Thu, 28 Jan 2016 22:24:27 +0000	[thread overview]
Message-ID: <36F6EBABA23FEF4391AF72944D228901EB6F1F59@BBYEXM01.pmc-sierra.internal> (raw)

Hi

I would like to attend LSF/MM 2016 to participate in discussions around the optimization of the block layer and memory management for low latency NVM technologies. I'd be very interested in discussions pertaining to where we can take the work being done to add polling into the block layer and tying that into file-systems and applications. I would also be keen to discuss how we might extend the recent work to facilitate large persistent memory regions to IO memory (e.g. PCIe devices with large, persistent, memory regions).

I am also keen to discuss topics associated with non-block based hardware devices including things like NVDIMM, OpenChannel SSDs and persistent memory exposed on PCIe devices.

I spend quite a bit of time working on elements of the block layer (especially NVMe), the RDMA stack and (more recently) the NVDIMM/PMEM/DAX sections of the kernel.

Cheers

Stephen

--
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:[~2016-01-28 22:24 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=36F6EBABA23FEF4391AF72944D228901EB6F1F59@BBYEXM01.pmc-sierra.internal \
    --to=stephen.bates@pmcs.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nvdimm@lists.01.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox