public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Roger While <simrw@sim-basis.de>
Cc: linux-kernel@vger.kernel.org, suresh.b.siddha@intel.com
Subject: Re: [patch 1/2] x86,fpu: split FPU state from task struct
Date: Sun, 24 Feb 2008 08:29:32 -0800	[thread overview]
Message-ID: <20080224162932.GB27194@linux-os.sc.intel.com> (raw)
In-Reply-To: <6.1.1.1.2.20080224082113.01e51e50@192.168.6.12>

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:
> >
> > 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.
> 
> >  	if (next_p->fpu_counter>5)
> > -		prefetch(&next->i387.fxsave);
> > +		prefetch(FXSAVE(next_p));
> 
> Shouldn't that be  prefetch(FXSAVE(next));  ?

No. 'next_p' which is the task_struct is what FXSAVE macro takes.

thanks,
suresh

  reply	other threads:[~2008-02-24 16:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-24  7:27 [patch 1/2] x86,fpu: split FPU state from task struct Roger While
2008-02-24 16:29 ` Siddha, Suresh B [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-24  2:34 Suresh Siddha
2008-02-24  3:04 ` Christoph Hellwig
2008-02-24  7:22 ` Ingo Molnar
2008-02-24 16:30   ` 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=20080224162932.GB27194@linux-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simrw@sim-basis.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