lkml.org 
[lkml]   [2018]   [Feb]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC PATCH V2 11/22] x86/intel_rdt: Associate pseudo-locked regions with its domain
On Mon, 19 Feb 2018, Reinette Chatre wrote:

> Hi Thomas,
>
> On 2/19/2018 1:19 PM, Thomas Gleixner wrote:
> > On Tue, 13 Feb 2018, Reinette Chatre wrote:
> >
> >> After a pseudo-locked region is locked it needs to be associated with
> >> the RDT domain representing the pseudo-locked cache so that its life
> >> cycle can be managed correctly.
> >>
> >> Only a single pseudo-locked region can exist on any cache instance so we
> >> maintain a single pointer to a pseudo-locked region from each RDT
> >> domain.
> >
> > Why is only a single pseudo locked region possible?
>
> The setup of a pseudo-locked region requires the usage of wbinvd. If a
> second pseudo-locked region is thus attempted it will evict the
> pseudo-locked data of the first.

Why does it neeed wbinvd? wbinvd is a big hammer. What's wrong with clflush?

Thanks,

tglx

\
 
 \ /
  Last update: 2018-02-20 00:20    [W:0.071 / U:11.232 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site