From: "H. Peter Anvin" <hpa@zytor.com>
To: Dan Williams <dan.j.williams@intel.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>,
Jeff Moyer <jmoyer@redhat.com>,
linux-nvdimm <linux-nvdimm@ml01.01.org>, X86 ML <x86@kernel.org>,
Dave Chinner <david@fromorbit.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, Jan Kara <jack@suse.com>
Subject: Re: [PATCH 0/2] "big hammer" for DAX msync/fsync correctness
Date: Fri, 6 Nov 2015 16:51:59 -0800 [thread overview]
Message-ID: <563D4B2F.9010608@zytor.com> (raw)
In-Reply-To: <CAPcyv4iptRuGb0O13+LN0Qv7XUDdJYG6TCJNOVMASDTLw90gtw@mail.gmail.com>
On 11/06/15 15:17, Dan Williams wrote:
>>
>> Is it really required to do that on all cpus?
>
> I believe it is, but I'll double check.
>
It's required on all CPUs on which the DAX memory may have been dirtied.
This is similar to the way we flush TLBs.
-hpa
next prev parent reply other threads:[~2015-11-07 0:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 22:09 [PATCH 0/2] "big hammer" for DAX msync/fsync correctness Ross Zwisler
2015-10-28 22:09 ` Ross Zwisler
2015-10-28 22:09 ` [PATCH 1/2] pmem: add wb_cache_pmem() to the PMEM API Ross Zwisler
2015-10-28 22:09 ` Ross Zwisler
2015-10-28 22:09 ` [PATCH 2/2] pmem: Add simple and slow fsync/msync support Ross Zwisler
2015-10-28 22:09 ` Ross Zwisler
2015-10-28 23:02 ` Dan Williams
2015-10-28 23:02 ` Dan Williams
2015-10-28 22:24 ` [PATCH 0/2] "big hammer" for DAX msync/fsync correctness Jeff Moyer
2015-10-28 22:49 ` Dan Williams
2015-10-28 22:51 ` Ross Zwisler
2015-11-05 23:59 ` Dan Williams
2015-11-06 8:06 ` Thomas Gleixner
2015-11-06 16:04 ` Dan Williams
2015-11-06 17:35 ` Thomas Gleixner
2015-11-06 23:17 ` Dan Williams
2015-11-07 0:51 ` H. Peter Anvin [this message]
2015-11-07 6:50 ` Thomas Gleixner
2015-11-07 8:12 ` Dan Williams
2015-11-07 8:38 ` Thomas Gleixner
2015-11-07 9:02 ` Dan Williams
2015-11-07 9:24 ` Thomas Gleixner
2015-11-06 20:25 ` H. Peter Anvin
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=563D4B2F.9010608@zytor.com \
--to=hpa@zytor.com \
--cc=dan.j.williams@intel.com \
--cc=david@fromorbit.com \
--cc=jack@suse.com \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=mingo@redhat.com \
--cc=ross.zwisler@linux.intel.com \
--cc=tglx@linutronix.de \
--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 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.