Re: [patch 1/2] x86,fpu: split FPU state from task struct

2008-02-24 Thread Siddha, Suresh B
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: > > > >

Re: [patch 1/2] x86,fpu: split FPU state from task struct

2008-02-24 Thread Siddha, Suresh B
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 optimiza

Re: [patch 1/2] x86,fpu: split FPU state from task struct

2008-02-23 Thread Roger While
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

Re: [patch 1/2] x86,fpu: split FPU state from task struct

2008-02-23 Thread Ingo Molnar
* 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

Re: [patch 1/2] x86,fpu: split FPU state from task struct

2008-02-23 Thread Christoph Hellwig
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

[patch 1/2] x86,fpu: split FPU state from task struct

2008-02-23 Thread Suresh Siddha
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 apps