From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
hpa@zytor.com, tglx@linutronix.de, andi@firstfloor.org,
linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@linux.intel.com>,
hch@infradead.org
Subject: Re: [patch 1/2] x86,fpu: split FPU state from task struct
Date: Sun, 24 Feb 2008 08:30:41 -0800 [thread overview]
Message-ID: <20080224163041.GC27194@linux-os.sc.intel.com> (raw)
In-Reply-To: <20080224072202.GB655@elte.hu>
On Sun, Feb 24, 2008 at 08:22:02AM +0100, Ingo Molnar wrote:
>
> * Suresh Siddha <suresh.b.siddha@intel.com> 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 FPU trap. This could save memory for non-fpu using apps.
> > Next patch does this lazy allocation.
> >
> > 2) allocate the right size for the actual cpu rather than 512 bytes
> > always. Patches enabling xsave/xrstor support (coming shortly) will
> > take advantage of this.
>
> i like the concept. Please clean up the issues found by Christoph and
> please also base it against x86.git#testing [this is clear 2.6.26
> material and there are already some changes in this area]:
>
> http://people.redhat.com/mingo/x86.git/README
Sure. Will do that in a day.
thanks,
suresh
next prev parent reply other threads:[~2008-02-24 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 2:34 [patch 1/2] x86,fpu: split FPU state from task struct Suresh Siddha
2008-02-24 2:34 ` [patch 2/2] x86,fpu: lazy allocation of FPU area Suresh Siddha
2008-02-24 3:08 ` Christoph Hellwig
2008-02-24 12:20 ` Andi Kleen
2008-02-24 16:32 ` Siddha, Suresh B
2008-02-24 3:04 ` [patch 1/2] x86,fpu: split FPU state from task struct Christoph Hellwig
2008-02-24 7:22 ` Ingo Molnar
2008-02-24 16:30 ` Siddha, Suresh B [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-24 7:27 Roger While
2008-02-24 16:29 ` Siddha, Suresh B
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080224163041.GC27194@linux-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=andi@firstfloor.org \
--cc=arjan@linux.intel.com \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox