From: Andi Kleen <ak@muc.de>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Andi Kleen <ak@muc.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fast path context switch - microoptimize FPU reload
Date: Sun, 9 Mar 2003 18:30:39 +0100 [thread overview]
Message-ID: <20030309173039.GA3098@averell> (raw)
In-Reply-To: <3E6B769D.2040602@colorfullife.com>
On Sun, Mar 09, 2003 at 06:15:09PM +0100, Manfred Spraul wrote:
> What about moving TIF_USEDFPU from the thread_info into
> task_struct->flags? This flag word is only accessed by "current", no
> special atomicity requirements.
There is still a PF_USEDFPU defined there that can be used.
I'll change it to using that.
But it would be a good idea to completely split the flags that are
changed externally like signals from only process local bits.
Then we could avoid the wasteful LOCK prefixes for everything local.
-Andi
next prev parent reply other threads:[~2003-03-09 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-09 17:15 [PATCH] Fast path context switch - microoptimize FPU reload Manfred Spraul
2003-03-09 17:30 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-09 16:39 Andi Kleen
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=20030309173039.GA3098@averell \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/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