On Sun, Feb 24, 2008 at 08:22:02AM +0100, Ingo Molnar wrote:
>
> * Suresh Siddha <[EMAIL PROTECTED]> wrote:
>
> > Split the FPU save area from the task struct. This allows easy
> > migration of FPU context, and it's generally cleaner. It also allows
> > the following two optimizations:
> >
>
On Sun, Feb 24, 2008 at 08:27:30AM +0100, Roger While wrote:
>
> On Sat, Feb 23, 2008 at 06:34:38PM -0800, Suresh Siddha wrote:
> > Split the FPU save area from the task struct. This allows easy migration
> > of FPU context, and it's generally cleaner. It also allows the following
> > two
On Sun, Feb 24, 2008 at 08:27:30AM +0100, Roger While wrote:
On Sat, Feb 23, 2008 at 06:34:38PM -0800, Suresh Siddha wrote:
Split the FPU save area from the task struct. This allows easy migration
of FPU context, and it's generally cleaner. It also allows the following
two optimizations:
On Sun, Feb 24, 2008 at 08:22:02AM +0100, Ingo Molnar wrote:
* Suresh Siddha [EMAIL PROTECTED] wrote:
Split the FPU save area from the task struct. This allows easy
migration of FPU context, and it's generally cleaner. It also allows
the following two optimizations:
1) only
On Sat, Feb 23, 2008 at 06:34:38PM -0800, Suresh Siddha wrote:
> Split the FPU save area from the task struct. This allows easy migration
> of FPU context, and it's generally cleaner. It also allows the following
> two optimizations:
>
> 1) only allocate when the application actually uses FPU,
* Suresh Siddha <[EMAIL PROTECTED]> wrote:
> Split the FPU save area from the task struct. This allows easy
> migration of FPU context, and it's generally cleaner. It also allows
> the following two optimizations:
>
> 1) only allocate when the application actually uses FPU, so in the
> first
On Sat, Feb 23, 2008 at 06:34:38PM -0800, Suresh Siddha wrote:
> Split the FPU save area from the task struct. This allows easy migration
> of FPU context, and it's generally cleaner. It also allows the following
> two optimizations:
>
> 1) only allocate when the application actually uses FPU, so
Split the FPU save area from the task struct. This allows easy migration
of FPU context, and it's generally cleaner. It also allows the following
two optimizations:
1) only allocate when the application actually uses FPU, so in the first
lazy FPU trap. This could save memory for non-fpu using
Split the FPU save area from the task struct. This allows easy migration
of FPU context, and it's generally cleaner. It also allows the following
two optimizations:
1) only allocate when the application actually uses FPU, so in the first
lazy FPU trap. This could save memory for non-fpu using
On Sat, Feb 23, 2008 at 06:34:38PM -0800, Suresh Siddha wrote:
Split the FPU save area from the task struct. This allows easy migration
of FPU context, and it's generally cleaner. It also allows the following
two optimizations:
1) only allocate when the application actually uses FPU, so in
* Suresh Siddha [EMAIL PROTECTED] wrote:
Split the FPU save area from the task struct. This allows easy
migration of FPU context, and it's generally cleaner. It also allows
the following two optimizations:
1) only allocate when the application actually uses FPU, so in the
first lazy
On Sat, Feb 23, 2008 at 06:34:38PM -0800, Suresh Siddha wrote:
Split the FPU save area from the task struct. This allows easy migration
of FPU context, and it's generally cleaner. It also allows the following
two optimizations:
1) only allocate when the application actually uses FPU, so in
12 matches
Mail list logo
