public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Matthew Wilcox <willy@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Boaz Harrosh <boaz@plexistor.com>, Christoph Hellwig <hch@lst.de>,
	Ross Zwisler <ross.zwisler@linux.intel.com>
Subject: Using pmem from a driver exposing a memory mapping (mmap) to userspace
Date: Tue, 28 Apr 2015 15:35:26 +0000 (UTC)	[thread overview]
Message-ID: <1364669203.39300.1430235326454.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <1918361018.39276.1430234930039.JavaMail.zimbra@efficios.com>

Hi!

I'm currently adaping lttng-modules to use DAX and pmem.
It will allow LTTng buffers to be recovered after a kernel
crash. I've moved pretty much all struct page pointers to
page frame numbers, as I remember being told that pmem does
not have struct page.

Now I'm looking into adapting my mmap and page fault handler
implementation (based on struct page) to a page-frame number
based implementation when the ring buffer is backed by
persistent memory, which will probably not require any page
fault handler at all when based by pmem+dax memory.

My current work is in this branch: https://github.com/compudj/lttng-modules-dev/tree/persistent-memory-buffers
(see last commits)

LTTng-modules supports both mmap() and splice(), but I plan
to only provide mmap() support for persistent memory, since
splice() really requires struct page.

Are there existing driver mmap implementations doing similar
things, or do you have recommendations on how to implement
this ?

Thanks,

Mathieu

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

       reply	other threads:[~2015-04-28 15:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1918361018.39276.1430234930039.JavaMail.zimbra@efficios.com>
2015-04-28 15:35 ` Mathieu Desnoyers [this message]
2015-04-29  7:06   ` Using pmem from a driver exposing a memory mapping (mmap) to userspace Boaz Harrosh
2015-04-30  0:25     ` Mathieu Desnoyers

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=1364669203.39300.1430235326454.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --cc=boaz@plexistor.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ross.zwisler@linux.intel.com \
    --cc=willy@linux.intel.com \
    /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