From: Christoph Hellwig <hch@lst.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: arnd@arndb.de, mingo@redhat.com, bp@alien8.de, hpa@zytor.com,
tglx@linutronix.de, ross.zwisler@linux.intel.com,
akpm@linux-foundation.org, jgross@suse.com, x86@kernel.org,
toshi.kani@hp.com, linux-nvdimm@lists.01.org,
benh@kernel.crashing.org, mcgrof@suse.com,
konrad.wilk@oracle.com, linux-kernel@vger.kernel.org,
stefan.bader@canonical.com, luto@amacapital.net,
linux-mm@kvack.org, geert@linux-m68k.org, ralf@linux-mips.org,
hmh@hmh.eng.br, mpe@ellerman.id.au, tj@kernel.org,
paulus@samba.org, Richard Weinberger <richard@nod.at>
Subject: Re: [PATCH v5 6/6] arch, x86: pmem api for ensuring durability of persistent memory updates
Date: Mon, 22 Jun 2015 18:17:54 +0200 [thread overview]
Message-ID: <20150622161754.GC8240@lst.de> (raw)
In-Reply-To: <20150622082449.35954.91411.stgit@dwillia2-desk3.jf.intel.com>
> +#ifdef ARCH_HAS_NOCACHE_UACCESS
Seems like this is always define for x86 anyway?
> +/**
> + * arch_memcpy_to_pmem - copy data to persistent memory
> + * @dst: destination buffer for the copy
> + * @src: source buffer for the copy
> + * @n: length of the copy in bytes
> + *
> + * Copy data to persistent memory media via non-temporal stores so that
> + * a subsequent arch_wmb_pmem() can flush cpu and memory controller
> + * write buffers to guarantee durability.
> + */
static inline void arch_memcpy_to_pmem(void __pmem *dst, const void *src, size_t n)
Too long line. Also why not simply arch_copy_{from,to}_pmem?
> +#else /* ARCH_HAS_NOCACHE_UACCESS i.e. ARCH=um */
Oh, UM. I'd rather see UM fixed to provide these.
Richard, any chance you could look into it?
> diff --git a/arch/x86/include/asm/io.h b/arch/x86/include/asm/io.h
> index 97ae3b748d9e..0d3e43f679aa 100644
> --- a/arch/x86/include/asm/io.h
> +++ b/arch/x86/include/asm/io.h
> @@ -249,6 +249,12 @@ static inline void flush_write_buffers(void)
> #endif
> }
>
> +static inline void __pmem *arch_memremap_pmem(resource_size_t offset,
> + unsigned long size)
> +{
> + return (void __force __pmem *) ioremap_cache(offset, size);
> +}
Now with my ioremap_flags proposal we'd just add an IOREMAP_PMEM
flag, which architectures could implement (usually as no-op), and move
the cast into memremap_pmem.
> + * These defaults seek to offer decent performance and minimize the
> + * window between i/o completion and writes being durable on media.
> + * However, it is undefined / architecture specific whether
> + * default_memremap_pmem + default_memcpy_to_pmem is sufficient for
> + * making data durable relative to i/o completion.
> + */
> +static void default_memcpy_to_pmem(void __pmem *dst, const void *src, size_t size)
> +{
> + memcpy((void __force *) dst, src, size);
> +}
This should really be in asm-generic (or at least your linux/pmem.h for now).
> +static void __pmem *default_memremap_pmem(resource_size_t offset, unsigned long size)
> +{
> + return (void __pmem *)memremap_wt(offset, size);
> +}
And this as well, unless we can get rid of it entirely with ioremap_flags().
> if (rw == READ) {
> - memcpy(mem + off, pmem->virt_addr + pmem_off, len);
> + memcpy_from_pmem(mem + off, pmem_addr, len);
> flush_dcache_page(page);
> } else {
> flush_dcache_page(page);
> - memcpy(pmem->virt_addr + pmem_off, mem + off, len);
> + if (arch_has_pmem_api())
> + memcpy_to_pmem(pmem_addr, mem + off, len);
> + else
> + default_memcpy_to_pmem(pmem_addr, mem + off, len);
So memcpy_from_pmem hides the different but memcpy_to_pmem doesn't?
That seems pretty awkward. Please move the check into the helper.
> + if (rw && arch_has_pmem_api())
> + wmb_pmem();
And here again make sure wmb_pmem is always available and a no-op if
not supported.
> + if (arch_has_pmem_api())
> + pmem->virt_addr = memremap_pmem(pmem->phys_addr, pmem->size);
> + else
> + pmem->virt_addr = default_memremap_pmem(pmem->phys_addr,
> + pmem->size);
All of this should be hidden in memremap_pmem.
--
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>
next prev parent reply other threads:[~2015-06-22 16:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 8:24 [PATCH v5 0/6] pmem api, generic ioremap_cache, and memremap Dan Williams
2015-06-22 8:24 ` [PATCH v5 1/6] arch, drivers: don't include <asm/io.h> directly, use <linux/io.h> instead Dan Williams
2015-06-22 16:01 ` Christoph Hellwig
2015-06-22 8:24 ` [PATCH v5 2/6] arch: unify ioremap prototypes and macro aliases Dan Williams
2015-06-22 16:10 ` Christoph Hellwig
2015-06-22 17:12 ` Dan Williams
2015-06-23 10:07 ` Christoph Hellwig
2015-06-23 15:04 ` Dan Williams
2015-06-24 12:24 ` Christoph Hellwig
2015-06-30 22:57 ` Dan Williams
2015-07-01 6:23 ` Christoph Hellwig
2015-07-01 6:55 ` Geert Uytterhoeven
2015-07-01 6:59 ` Christoph Hellwig
2015-07-01 7:19 ` Geert Uytterhoeven
2015-07-01 7:28 ` Christoph Hellwig
2015-07-07 9:50 ` Luis R. Rodriguez
2015-07-07 10:13 ` Russell King - ARM Linux
2015-07-07 10:27 ` Geert Uytterhoeven
2015-07-07 16:07 ` Luis R. Rodriguez
2015-07-07 23:10 ` Toshi Kani
2015-07-09 1:40 ` Luis R. Rodriguez
2015-07-09 23:43 ` Toshi Kani
2015-07-01 8:09 ` Russell King - ARM Linux
2015-07-01 16:47 ` Dan Williams
2015-07-09 18:54 ` Luis R. Rodriguez
2015-06-22 8:24 ` [PATCH v5 3/6] cleanup IORESOURCE_CACHEABLE vs ioremap() Dan Williams
2015-06-22 8:24 ` [PATCH v5 4/6] devm: fix ioremap_cache() usage Dan Williams
2015-06-22 8:24 ` [PATCH v5 5/6] arch: introduce memremap_cache() and memremap_wt() Dan Williams
2015-06-22 8:24 ` [PATCH v5 6/6] arch, x86: pmem api for ensuring durability of persistent memory updates Dan Williams
2015-06-22 16:17 ` Christoph Hellwig [this message]
2015-06-22 17:51 ` Dan Williams
2015-06-23 10:09 ` Christoph Hellwig
2015-06-23 10:39 ` Richard Weinberger
2015-06-24 12:08 ` Christoph Hellwig
2015-06-24 12:35 ` Richard Weinberger
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=20150622161754.GC8240@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=geert@linux-m68k.org \
--cc=hmh@hmh.eng.br \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=luto@amacapital.net \
--cc=mcgrof@suse.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=richard@nod.at \
--cc=ross.zwisler@linux.intel.com \
--cc=stefan.bader@canonical.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=toshi.kani@hp.com \
--cc=x86@kernel.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).