linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mikulas Patocka <mpatocka@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>,
	linux-mm@kvack.org, linux-nvdimm@lists.01.org,
	Dan Williams <dan.j.williams@intel.com>,
	dm-devel@redhat.com, Laura Abbott <labbott@redhat.com>,
	Christoph Hellwig <hch@lst.de>,
	"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH] vmalloc: introduce vmap_pfn for persistent memory
Date: Wed, 8 Nov 2017 07:33:09 -0500 (EST)	[thread overview]
Message-ID: <alpine.LRH.2.02.1711080725490.12294@file01.intranet.prod.int.rdu2.redhat.com> (raw)
In-Reply-To: <20171108095909.GA7390@infradead.org>



On Wed, 8 Nov 2017, Christoph Hellwig wrote:

> On Tue, Nov 07, 2017 at 05:03:11PM -0500, Mikulas Patocka wrote:
> > Hi
> > 
> > I am developing a driver that uses persistent memory for caching. A 
> > persistent memory device can be mapped in several discontiguous ranges.
> > 
> > The kernel has a function vmap that takes an array of pointers to pages 
> > and maps these pages to contiguous linear address space. However, it can't 
> > be used on persistent memory because persistent memory may not be backed 
> > by page structures.
> > 
> > This patch introduces a new function vmap_pfn, it works like vmap, but 
> > takes an array of pfn_t - so it can be used on persistent memory.
> 
> How is cache flushing going to work for this interface assuming
> that your write to/from the virtual address and expect it to be
> persisted on pmem?

We could use the function clwb() (or arch-independent wrapper dax_flush()) 
- that uses the clflushopt instruction on Broadwell or clwb on Skylake - 
but it is very slow, write performance on Broadwell is only 350MB/s.

So in practice I use the movnti instruction that bypasses cache. The 
write-combining buffer is flushed with sfence.

Mikulas

--
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:[~2017-11-08 12:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07 22:03 [PATCH] vmalloc: introduce vmap_pfn for persistent memory Mikulas Patocka
2017-11-08  9:59 ` Christoph Hellwig
2017-11-08 12:33   ` Mikulas Patocka [this message]
2017-11-08 15:04     ` Christoph Hellwig
2017-11-08 15:21       ` Mikulas Patocka
2017-11-08 15:35         ` [dm-devel] " Christoph Hellwig
2017-11-08 15:41           ` Dan Williams
2017-11-08 20:15             ` Mikulas Patocka
2017-11-08 20:25               ` Dan Williams
2017-11-09 16:40                 ` Mikulas Patocka
2017-11-09 16:45                   ` Dan Williams
2017-11-09 17:30                     ` Mikulas Patocka
2017-11-09 17:35                       ` Dan Williams
2017-11-08 17:42           ` Mikulas Patocka
2017-11-08 17:47             ` Christoph Hellwig
2017-11-08 20:26               ` Mikulas Patocka
2017-11-08 21:26                 ` Dan Williams
2017-11-09 16:37                   ` Mikulas Patocka
2017-11-09 16:49                     ` Dan Williams
2017-11-09 18:13                       ` Mikulas Patocka
2017-11-09 18:38                         ` Dan Williams
2017-11-09 18:51                           ` Mikulas Patocka
2017-11-09 18:58                             ` Dan Williams

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=alpine.LRH.2.02.1711080725490.12294@file01.intranet.prod.int.rdu2.redhat.com \
    --to=mpatocka@redhat.com \
    --cc=dan.j.williams@intel.com \
    --cc=dm-devel@redhat.com \
    --cc=hch@infradead.org \
    --cc=hch@lst.de \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=labbott@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=ross.zwisler@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;
as well as URLs for NNTP newsgroup(s).