From: Boaz Harrosh <boaz@plexistor.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Matthew Wilcox <willy@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
Ross Zwisler <ross.zwisler@linux.intel.com>
Subject: Re: Using pmem from a driver exposing a memory mapping (mmap) to userspace
Date: Wed, 29 Apr 2015 10:06:53 +0300 [thread overview]
Message-ID: <5540830D.7030006@plexistor.com> (raw)
In-Reply-To: <1364669203.39300.1430235326454.JavaMail.zimbra@efficios.com>
On 04/28/2015 06:35 PM, Mathieu Desnoyers wrote:
> 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.
There will be page-faults at lease once for every combination
of application+page. Sure there may only be one per a+p
until the application does a close on the file.
Your job can be simple if you use the pmem's inode. You know
how each block-device is a mini file system with a single file.
Use bdev->bd_inode to get to the one inode associated with
your pmem bdev. Well this inode is IS_DAX(), so if you supply
your own get_block() function to the DAX handlers you need
not duplicate any mmap code at all.
(You can also use the same DAX infrastructure for the read/write_iter
implementation)
>
> 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.
>
No splice just works fine. In-fact a NULL .splice_XXX vector
will use the default_file_splice_read/write which does a
copy and uses your regular read/write_iter vectors. So
leave the .splice NULL and it will be supported by your
read/write_iter interface.
> Are there existing driver mmap implementations doing similar
> things, or do you have recommendations on how to implement
> this ?
>
DAX.c lib does all that you need. You only need your own
translation from your device files to a chunk of pmem.
Its how I'd do it, good luck. CC me on the patches I'll
review them.
Cheers
Boaz
> Thanks,
> Mathieu
next prev parent reply other threads:[~2015-04-29 7:06 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 ` Using pmem from a driver exposing a memory mapping (mmap) to userspace Mathieu Desnoyers
2015-04-29 7:06 ` Boaz Harrosh [this message]
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=5540830D.7030006@plexistor.com \
--to=boaz@plexistor.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--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 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.