Re: remap allocator for per-CPU memory

[Tejun Heo <teheo@novell.com>]

Hello,

Jan Beulich wrote:
> I think the only two alternatives are
> 
> (a) don't use large pages in the first place here, or

Seems like the first candidate at the moment.

> (b) teach the pageattr code to handle the per-CPU virtual area similarly to
> the kernel space for x86-64 (though it's going to be a little more complicated
> since there's no pre-determined relation between the virtual and physical
> addresses - the necessary lookup might become expensive on systems with
> very many [possible] CPUs).

Can you elaborate this a bit?  Let's sya there's quick way to match
whether the page is part of the remapped large page, what can pageattr
do differently then?  Applying the same attribute to both mappings?
Failing or filtering set_memory_*()?

Thanks.

-- 
tejun