mlock in cache

Andrew Haley aph@redhat.com
Fri Aug 2 20:29:00 GMT 2013


On 08/02/2013 09:02 PM, Christos wrote:
>  >>> On Fri, Aug 2, 2013 at 5:32 PM, Andrew Haley <aph@redhat.com 
> <mailto:aph@redhat.com>> wrote:
>  >>On 08/02/2013 06:06 PM, Christos Tsopokis wrote:
>  >On Fri, Aug 2, 2013 at 8:09 PM, Andrew Haley <aph@redhat.com 
> <mailto:aph@redhat.com>> wrote:
>  >>
>  >>> And why do you think that there must be a way to achieve it?  If it
>  >>> exists, it's in that manual.
>  >>
>  >> Well, it's obviously more complicated than that. When I refer to APIs, I
>  >> refer even to the information the manufacturers provide.
> 
>  >Indeed, that's what that manual I provided is.
> 
> Exactly, and because the manufacturers do not provide some instructions 
> for something like that (at least I didn't manage to find one), then you 
> have to play directly with MMU. ;-)

And how do you propose to play directly with MMU?  In a way that isn't
described in the manual?

>  >Again, I don't believe that what you seek exists, and I can think
>  >of good reasons why it doesn't.
> 
> If you look carefully Oleg's answer (or even in the link I provided a 
> few hours ago) you will see that in some architectures it does exist.

Sure, but I'm talking about readily-available CPUs that you might have
in your desktop computer.  Were you not?

Andrew.



More information about the Gcc-help mailing list