[OpenSPARC-T2-SAM] / sam-t2 / sam / docs / ui-cmds / cmd_mips.html

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html>
<head>
<title>SPARC Architectural Model: User Commands</title>
</head>
<body bgcolor="#FFFFFF" LANG="en-US">
<div STYLE="margin-bottom: 0cm"></div>&nbsp;

<h2>
mips
</h2>

<h4>
NAME
</h4>
<ul>
mips - display simulated mips
</ul>

<h4>SYNOPSIS</h4>
<tt>
<ul>
mips
</ul>
</tt>

<h4>DESCRIPTION</h4>
<ul>
The mips command displays the simulated system's simulated mips
which is simulated instructions per simulated second.  This differs
from simulated instructions per wall-clock second which is provided by
the <a href="cmd_perf.html">perf</a> command.
<p>
The mips output is the average over all the cpus/strands being
simulated, in other words it is the speed of the cpus not their
aggregate throughput.
<P>
The reason for having the "mips" command is that when "conf 
and "conf kmips" have been set to different values then the
overall system mips depends on the ratio of user to kernel
instructions. otherwise the "mips" output will 
match the "conf mips" parameter, however you do still get to
see the user/kernel ratio dynamically.
</ul>

<h4>RETURN VALUES</h4>
<ul>
Simulated instructions per simulated second.
</ul>

<h4>SEE ALSO</h4>
<ul><a href="cmd_conf.html">conf</a> mips</ul>
<ul><a href="cmd_conf.html">conf</a> umips</ul>
<ul><a href="cmd_conf.html">conf</a> kmips</ul>
<ul><a href="cmd_perf.html">perf</a>
</ul>
<hr>
</body>
</html>
Commit	Line	Data
920dae64 AT	1	<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
	2	<html>
	3	<head>
	4	<title>SPARC Architectural Model: User Commands</title>
	5	</head>
	6	<body bgcolor="#FFFFFF" LANG="en-US">
	7	<div STYLE="margin-bottom: 0cm"></div>
	8
	9	<h2>
	10	mips
	11	</h2>
	12
	13	<h4>
	14	NAME
	15	</h4>
	16	<ul>
	17	mips - display simulated mips
	18	</ul>
	19
	20	<h4>SYNOPSIS</h4>
	21	<tt>
	22	<ul>
	23	mips
	24	</ul>
	25	</tt>
	26
	27	<h4>DESCRIPTION</h4>
	28	<ul>
	29	The mips command displays the simulated system's simulated mips
	30	which is simulated instructions per simulated second. This differs
	31	from simulated instructions per wall-clock second which is provided by
	32	the <a href="cmd_perf.html">perf</a> command.
	33	<p>
	34	The mips output is the average over all the cpus/strands being
	35	simulated, in other words it is the speed of the cpus not their
	36	aggregate throughput.
	37	<P>
	38	The reason for having the "mips" command is that when "conf
	39	and "conf kmips" have been set to different values then the
	40	overall system mips depends on the ratio of user to kernel
	41	instructions. otherwise the "mips" output will
	42	match the "conf mips" parameter, however you do still get to
	43	see the user/kernel ratio dynamically.
	44	</ul>
	45
	46	<h4>RETURN VALUES</h4>
	47	<ul>
	48	Simulated instructions per simulated second.
	49	</ul>
	50
	51	<h4>SEE ALSO</h4>
	52	<ul><a href="cmd_conf.html">conf</a> mips</ul>
	53	<ul><a href="cmd_conf.html">conf</a> umips</ul>
	54	<ul><a href="cmd_conf.html">conf</a> kmips</ul>
	55	<ul><a href="cmd_perf.html">perf</a>
	56	</ul>
	57	<hr>
	58	</body>
	59	</html>