From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966183AbbKFRgO (ORCPT ); Fri, 6 Nov 2015 12:36:14 -0500 Received: from www.linutronix.de ([62.245.132.108]:60924 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755568AbbKFRgF (ORCPT ); Fri, 6 Nov 2015 12:36:05 -0500 Date: Fri, 6 Nov 2015 18:35:11 +0100 (CET) From: Thomas Gleixner To: Dan Williams cc: Ross Zwisler , Jeff Moyer , linux-nvdimm , X86 ML , Dave Chinner , "linux-kernel@vger.kernel.org" , Ingo Molnar , "H. Peter Anvin" , Jan Kara Subject: Re: [PATCH 0/2] "big hammer" for DAX msync/fsync correctness In-Reply-To: Message-ID: References: <1446070176-14568-1-git-send-email-ross.zwisler@linux.intel.com> <20151028225112.GA30284@linux.intel.com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001,URIBL_BLOCKED=0.001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 6 Nov 2015, Dan Williams wrote: > On Fri, Nov 6, 2015 at 12:06 AM, Thomas Gleixner wrote: > > Just for the record. Such a flush mechanism with > > > > on_each_cpu() > > wbinvd() > > ... > > > > will make that stuff completely unusable on Real-Time systems. We've > > been there with the big hammer approach of the intel graphics > > driver. > > Noted. This means RT systems either need to disable DAX or avoid > fsync. Yes, this is a wart, but not an unexpected one in a first > generation persistent memory platform. And it's not just only RT. The folks who are aiming for 100% undisturbed user space (NOHZ_FULL) will be massively unhappy about that as well. Is it really required to do that on all cpus? Thanks, tglx