From: Christoph Hellwig <hch@lst.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "Christoph Hellwig" <hch@lst.de>,
"Ross Zwisler" <ross.zwisler@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Paul Mackerras" <paulus@samba.org>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Jens Axboe" <axboe@kernel.dk>,
"Martin Schwidefsky" <schwidefsky@de.ibm.com>,
"Heiko Carstens" <heiko.carstens@de.ibm.com>,
linux390@de.ibm.com, "Alexander Viro" <viro@zeniv.linux.org.uk>,
"Matthew Wilcox" <willy@linux.intel.com>,
"Jeff Layton" <jlayton@primarydata.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Omar Sandoval" <osandov@osandov.com>,
"Boaz Harrosh" <boaz@plexistor.com>,
"Miklos Szeredi" <mszeredi@suse.cz>, "Jan Kara" <jack@suse.cz>,
"Wolfram Sang" <wsa@the-dreams.de>
Subject: Re: [PATCH v2 7/7] pmem, dax: have direct_access use __pmem annotation
Date: Sat, 15 Aug 2015 18:00:55 +0200 [thread overview]
Message-ID: <20150815160055.GB26248@lst.de> (raw)
In-Reply-To: <CAPcyv4gHatJxtJ_Utc07L-EiX0f=SnkEoAVsB9PNDhtwmxrobQ@mail.gmail.com>
On Sat, Aug 15, 2015 at 08:44:27AM -0700, Dan Williams wrote:
> That said, while we don't need special accessors we do need guarantees
> that anything that has written to a persistent memory address has done
> so in a way that wmb_pmem() is able to flush it. It's more of a "I've
> audited this code path for wmb_pmem() compatibility so use this api to
> write to pmem."
I'm more worried about things where don't just do plain loads and stores
to a pmem region but DMA, which will end up as a nightmare of casts.
But we can wait and see how that evolves in the end..
next prev parent reply other threads:[~2015-08-15 16:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 16:51 [PATCH v2 0/7] dax: I/O path enhancements Ross Zwisler
2015-08-13 16:51 ` [PATCH v2 6/7] dax: update I/O path to do proper PMEM flushing Ross Zwisler
2015-08-13 21:11 ` Dan Williams
2015-08-14 16:48 ` Ross Zwisler
2015-08-13 16:51 ` [PATCH v2 7/7] pmem, dax: have direct_access use __pmem annotation Ross Zwisler
2015-08-13 21:20 ` Dan Williams
2015-08-14 16:55 ` Ross Zwisler
2015-08-14 16:58 ` Dan Williams
2015-08-15 9:11 ` Christoph Hellwig
2015-08-15 15:49 ` Dan Williams
2015-08-15 9:19 ` Christoph Hellwig
2015-08-15 15:44 ` Dan Williams
2015-08-15 16:00 ` Christoph Hellwig [this message]
2015-08-15 18:05 ` Dan Williams
2015-08-17 20:07 ` Ross Zwisler
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=20150815160055.GB26248@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=benh@kernel.crashing.org \
--cc=boaz@plexistor.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jack@suse.cz \
--cc=jlayton@primarydata.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux390@de.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=mszeredi@suse.cz \
--cc=osandov@osandov.com \
--cc=paulus@samba.org \
--cc=ross.zwisler@linux.intel.com \
--cc=schwidefsky@de.ibm.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@linux.intel.com \
--cc=wsa@the-dreams.de \
/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).