From: rwhron@earthlink.net
To: alan@lxorguk.ukuu.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [2.4] [2.5] [i386] Add support for GCC 3.1
Date: Mon, 27 May 2002 12:55:47 -0400 [thread overview]
Message-ID: <20020527125547.A29216@rushmore> (raw)
>> Adding CONFIG_XF86_USE_3DNOW=y
>> seems to help a little too.
Mmm, maybe not.
> Make sure you benchmark FPU intensive use when testing USE_3DNOW. I've
> seen several situations where it looks marginally better until you
> actually measure two things - memory bandwidth available to user
> programs, and also FPU performance, especially of FPU heavy apps that
> schedule a lot (eg Quake)
Thanks for helping me narrow the search. On an allocate and write to
pages of memory test, USE_3DNOW increased test time by 15% (which is
bad) on k6-2.
Both kernels compiled with gcc-3.1.0 -march=k6-2.
mtest01 -w 50 executed 100 times
CONFIG_X86_USE_3DNOW=n 745 seconds
CONFIG_X86_USE_3DNOW=y 860 seconds
--
Randy Hron
next reply other threads:[~2002-05-27 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 16:55 rwhron [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-26 20:02 [PATCH] [2.4] [2.5] [i386] Add support for GCC 3.1 rwhron
2002-05-26 21:36 ` Alan Cox
2002-05-26 22:10 ` Dave Jones
2002-05-27 11:44 ` Christopher E. Brown
2002-05-29 13:44 ` Dave Jones
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=20020527125547.A29216@rushmore \
--to=rwhron@earthlink.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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