From: Fenghua Yu <fenghua.yu@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Tony Luck <tony.luck@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
"H. Peter Anvin" <h.peter.anvin@intel.com>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT pull] x86/cache: Updates for 4.10
Date: Wed, 21 Dec 2016 13:31:37 -0800 [thread overview]
Message-ID: <20161221213136.GB56305@linux.intel.com> (raw)
In-Reply-To: <20161221210119.GA56305@linux.intel.com>
On Tue, Dec 13, 2016, Thomas Gleixner <tglx@linutronix.de> wrote:
> On Mon, 12 Dec 2016, Linus Torvalds wrote:
> On Mon, Dec 12, 2016 at 1:53 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
>> It looks pretty self-contained (good), but it also looks majorly
>> strange. I will have to think about this. What are the main/expected
>> users?
> - Virtualization so a VM can only trash only the associated part of the
> cash w/o disturbing others
>
> - Real-Time systems to seperate RT and general workloads.
>
> - Latency sensitive enterprise workloads
>
> - In theory this also can be used to protect against cache side channel
> attacks.
Quite a few companies and research groups are interested in the hardware
feature and/or the resctrl file system interface. They do demonstrate
performance and QoS improvements in real-time, VM, and native Linux
by partitioning cache for processes to avoid noisy neighbors.
Thanks.
-Fenghua
next parent reply other threads:[~2016-12-21 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161221210119.GA56305@linux.intel.com>
2016-12-21 21:31 ` Fenghua Yu [this message]
2016-12-12 9:53 [GIT pull] x86/cache: Updates for 4.10 Thomas Gleixner
2016-12-13 4:26 ` Linus Torvalds
2016-12-13 8:04 ` Peter Zijlstra
2016-12-13 9:01 ` Thomas Gleixner
2016-12-17 1:44 ` Tony Luck
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=20161221213136.GB56305@linux.intel.com \
--to=fenghua.yu@intel.com \
--cc=h.peter.anvin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.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).