From: Chuck Ebbert <76306.1226@compuserve.com>
To: Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 2.6.13-rc3a] i386: inline restore_fpu
Date: Fri, 22 Jul 2005 05:58:44 -0400 [thread overview]
Message-ID: <200507220602_MC3-1-A540-A73D@compuserve.com> (raw)
On Fri, 22 Jul 2005 at13:27:56 +1000, Andrew Morton wrote:
> hm. What context switch rate is that thing doing?
23000 - 25000 / second. I guess that explains why my attempt to
duplicate this in C failed -- it switches at 15-19 times per second:
/* i387 context switch benchmark
* compile this program without optimization
*/
#include <sys/types.h>
#include <sys/wait.h>
#include <unistd.h>
#include <stdio.h>
#include <signal.h>
#include <sched.h>
int lo = 0, fp = 0, af = 0;
long i, iters;
pid_t child;
cpu_set_t cpuset;
void handler(int sig) {
lo = 0; /* stop looping */
}
struct sigaction sa = {
.sa_handler = handler,
};
main(int argc, char *argv[]) {
if (argc < 2) /* mandatory loop iteration count */
exit(1);
iters = atol(argv[1]);
if (argc > 2) /* loop in parent while waiting for child to exit */
lo = atoi(argv[2]);
if (argc > 3) /* use FP while wait-looping */
fp = atoi(argv[3]);
if (argc > 4) /* use cpu affinity -- all code runs on cpu 0 */
af = atoi(argv[4]);
__CPU_SET(0, &cpuset);
child = fork();
if (child) { /* parent */
if (af)
sched_setaffinity(0, &cpuset);
if (lo) {
sigaction(SIGCHLD, &sa, NULL);
if (fp)
__asm__ __volatile__("fld1" "\n\t" "fldz");
while (lo)
if (fp)
__asm__ __volatile__(
"fadd %st(1), %st(0)");
} else
wait(NULL);
} else { /* child */
if (af)
sched_setaffinity(0, &cpuset);
__asm__ __volatile__("fld1" "\n\t" "fldz");
for (i = 0; i < iters; i++)
__asm__ __volatile__("fadd %st(1), %st(0)");
}
}
> Is the benchmark actually doing floating point stuff?
They only release .class files. ISTR java does FP math even when
developers think they are doing integer math but I can't find any
references.
__
Chuck
next reply other threads:[~2005-07-22 10:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 9:58 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-27 1:40 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
2005-07-24 12:56 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 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=200507220602_MC3-1-A540-A73D@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
Powered by JetHome