On Wed, 2007-03-21 at 10:49 -0600, Eric W. Biederman wrote:
> Rusty Russell <[EMAIL PROTECTED]> writes:
>
> > On Wed, 2007-03-21 at 03:21 -0600, Eric W. Biederman wrote:
> >> Do we really want to allow modules to be able to allocate page sized
> >> per cpu memory.
> >
> > Hi Eric!
> >
> > They
Rusty Russell <[EMAIL PROTECTED]> writes:
> On Wed, 2007-03-21 at 03:21 -0600, Eric W. Biederman wrote:
>> Do we really want to allow modules to be able to allocate page sized
>> per cpu memory.
>
> Hi Eric!
>
> They always could, of course, they just wouldn't get correct alignment.
> I thin
On Wed, 2007-03-21 at 03:21 -0600, Eric W. Biederman wrote:
> Do we really want to allow modules to be able to allocate page sized
> per cpu memory.
Hi Eric!
They always could, of course, they just wouldn't get correct alignment.
I think the principle of least surprise says that if we sup
Rusty Russell <[EMAIL PROTECTED]> writes:
> [This was part of the GDT cleanups and per-cpu-> pda changes, which I
> have revised, but this stands on its own. The only change is catching
> the x86-64 per-cpu allocator too].
> ==
> Let's allow page-alignment in general for per-cpu data (wanted by X
[This was part of the GDT cleanups and per-cpu-> pda changes, which I
have revised, but this stands on its own. The only change is catching
the x86-64 per-cpu allocator too].
==
Let's allow page-alignment in general for per-cpu data (wanted by Xen,
and Ingo suggested KVM as well).
Because larger
5 matches
Mail list logo