From: David Laight <David.Laight@ACULAB.COM>
To: 'Reinette Chatre' <reinette.chatre@intel.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"fenghua.yu@intel.com" <fenghua.yu@intel.com>,
"bp@alien8.de" <bp@alien8.de>,
"tony.luck@intel.com" <tony.luck@intel.com>
Cc: "mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 00/10] x86/CPU and x86/resctrl: Support pseudo-lock regions spanning L2 and L3 cache
Date: Thu, 27 Jun 2019 09:12:40 +0000 [thread overview]
Message-ID: <41cd71514a9042abaaef909d816e2522@AcuMS.aculab.com> (raw)
In-Reply-To: <cover.1561569068.git.reinette.chatre@intel.com>
From: Reinette Chatre
> Sent: 26 June 2019 18:49
>
> Cache pseudo-locking involves preloading a region of physical memory into a
> reserved portion of cache that no task or CPU can subsequently fill into and
> from that point on will only serve cache hits. At this time it is only
> possible to create cache pseudo-locked regions in either L2 or L3 cache,
> supporting systems that support either L2 Cache Allocation Technology (CAT)
> or L3 CAT because CAT is the mechanism used to manage reservations of cache
> portions.
While this is a 'nice' hardware feature for some kinds of embedded systems
I don't see how it can be sensibly used inside a Linux kernel.
There are an awful lot of places where things can go horribly wrong.
I can imagine:
- Multiple requests to lock regions that end up trying to use the same
set-associative cache lines leaving none for normal operation.
- Excessive cache line bouncing because fewer lines are available.
- The effect of cache invalidate requests for the locked addresses.
- I suspect the Linux kernel can do full cache invalidates at certain times.
You've not given a use case.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2019-06-27 9:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 17:48 Reinette Chatre
2019-06-26 17:48 ` [PATCH 01/10] x86/CPU: Expose if cache is inclusive of lower level caches Reinette Chatre
2019-06-26 17:48 ` [PATCH 02/10] x86/resctrl: Remove unnecessary size compute Reinette Chatre
2019-06-26 17:48 ` [PATCH 03/10] x86/resctrl: Constrain C-states during pseudo-lock region init Reinette Chatre
2019-06-26 17:48 ` [PATCH 04/10] x86/resctrl: Set cache line size using new utility Reinette Chatre
2019-06-26 17:48 ` [PATCH 05/10] x86/resctrl: Associate pseudo-locked region's cache instance by id Reinette Chatre
2019-06-26 17:48 ` [PATCH 06/10] x86/resctrl: Introduce utility to return pseudo-locked cache portion Reinette Chatre
2019-06-26 17:48 ` [PATCH 07/10] x86/resctrl: Remove unnecessary pointer to pseudo-locked region Reinette Chatre
2019-06-26 17:48 ` [PATCH 08/10] x86/resctrl: Support pseudo-lock regions spanning resources Reinette Chatre
2019-06-26 17:48 ` [PATCH 09/10] x86/resctrl: Pseudo-lock portions of multiple resources Reinette Chatre
2019-06-26 17:48 ` [PATCH 10/10] x86/resctrl: Only pseudo-lock L3 cache when inclusive Reinette Chatre
2019-06-27 9:12 ` David Laight [this message]
2019-06-27 17:55 ` [PATCH 00/10] x86/CPU and x86/resctrl: Support pseudo-lock regions spanning L2 and L3 cache Reinette Chatre
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=41cd71514a9042abaaef909d816e2522@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@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