From: Peter Zijlstra <peterz@infradead.org>
To: John Ogness <john.ogness@linutronix.de>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
Sebastian Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, fenghua.yu@intel.com, h.peter.anvin@intel.com,
vikas.shivappa@linux.intel.com, tony.luck@intel.com,
davidcc@google.com, dave.hansen@intel.com, eranian@google.com
Subject: Re: [PATCHv2] x86/mm/cpa: avoid wbinvd() for PREEMPT
Date: Mon, 30 Jan 2017 13:31:28 +0100 [thread overview]
Message-ID: <20170130123128.GJ6515@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <87o9ypvt1q.fsf@linutronix.de>
On Mon, Jan 30, 2017 at 09:41:21AM +0100, John Ogness wrote:
> Although wbinvd() is faster than flushing many individual pages, it
> blocks the memory bus for "long" periods of time (>100us), thus
> directly causing unusually large latencies on all CPUs, regardless
> of any CPU isolation features that may be active.
>
> For 1024 pages, flushing those pages individually can take up to
> 2200us, but the task remains fully preemptible during that time.
>
> Signed-off-by: John Ogness <john.ogness@linutronix.de>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
I think we need an additional patch to deal with CAT, but we can easily
do that later.
I've thought about that situation a bit and wbinvd cannot and must not
respect the CAT mask because while all the new lines brought in by the
current context are constrained, lines shared with another context, or
if the current context changed might well be outside the current mask.
In any case, this is a unprivileged interface, and therefore I feel we
need to remove the wbinvd usage entirely, esp. if CAT is enabled.
But like said, we can do that in a follow up patch.
prev parent reply other threads:[~2017-01-30 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 8:41 John Ogness
2017-01-30 12:31 ` Peter Zijlstra [this message]
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=20170130123128.GJ6515@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bigeasy@linutronix.de \
--cc=dave.hansen@intel.com \
--cc=davidcc@google.com \
--cc=eranian@google.com \
--cc=fenghua.yu@intel.com \
--cc=h.peter.anvin@intel.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=vikas.shivappa@linux.intel.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
Powered by JetHome