From: Kenneth Parrish <Kenneth.Parrish@family-bbs.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch 2.6.13-rc3a] i386: inline restore_fpu
Date: 24 Jul 2005 12:56:36 GMT [thread overview]
Message-ID: <803f51.f83f12@family-bbs.org> (raw)
-=> Linus Torvalds wrote to All and Chuck Ebbert <=-
[..]
Chuck>
> "m" ((tsk)->thread.i387.fxsave))
>
> because that's the largest possible operand that could end up
> being read?
LT> Yes, I ended up fixing that already (along with handling the fxsave
LT> case too).
[..]
2.6.13-rc3-git5 lags -git4 on nbench's bitfield test, a part of its
memory index, eg typical runs
-git5
BITFIELD : 1.1589e+07 : 1.99 : 0.42
-git4
BITFIELD : 2.1892e+07 : 3.76 : 0.78
lmbench has slower context switch numbers for -git5.
--- MultiMail/Linux v0.46
next reply other threads:[~2005-07-24 12:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-24 12:56 Kenneth Parrish [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-27 1:40 [patch 2.6.13-rc3a] i386: inline restore_fpu linux
2005-07-26 21:23 Chuck Ebbert
2005-07-26 21:47 ` Linus Torvalds
2005-07-26 21:23 Chuck Ebbert
2005-07-25 2:34 Kenneth Parrish
[not found] <200507212309_MC3-1-A534-95EF@compuserve.com.suse.lists.linux.kernel>
[not found] ` <20050722132756.578acca7.akpm@osdl.org.suse.lists.linux.kernel>
2005-07-23 15:35 ` Andi Kleen
2005-07-23 7:09 Chuck Ebbert
2005-07-23 17:33 ` Linus Torvalds
2005-07-23 7:09 Chuck Ebbert
2005-07-23 17:38 ` Linus Torvalds
2005-07-23 17:46 ` Arjan van de Ven
2005-07-23 18:02 ` Linus Torvalds
2005-07-22 9:58 Chuck Ebbert
2005-07-22 3:06 Chuck Ebbert
2005-07-22 3:27 ` Andrew Morton
2005-07-22 5:22 ` Linus Torvalds
2005-07-22 11:23 ` Arjan van de Ven
2005-07-22 8:14 ` Adrian Bunk
2005-07-22 18:13 ` Linus Torvalds
2005-07-25 19:26 ` Bill Davidsen
2005-07-22 23:19 ` Linus Torvalds
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=803f51.f83f12@family-bbs.org \
--to=kenneth.parrish@family-bbs.org \
--cc=linux-kernel@vger.kernel.org \
/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