summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorYujun Zhang <zhang.yujunz@zte.com.cn>2016-10-31 06:50:59 +0000
committerGerrit Code Review <gerrit@opnfv.org>2016-10-31 06:50:59 +0000
commitb5556d145c049121c20c148ce9b35f39961b2171 (patch)
treecb3a5fcacaaacc32abd477336ab9dfaf8e9ea4be /docs
parent7c22ae6e43c211ed4386a61b3070de423034ca9c (diff)
parent2b6cdda870558b2946fdbd4733293942335c0713 (diff)
Merge "Small amends in the documentation."
Diffstat (limited to 'docs')
-rw-r--r--docs/userguide/_01-compute.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/userguide/_01-compute.rst b/docs/userguide/_01-compute.rst
index 7cd4c2ce..56be5488 100644
--- a/docs/userguide/_01-compute.rst
+++ b/docs/userguide/_01-compute.rst
@@ -58,7 +58,7 @@ OpenSSL Speed
OpenSSL Speed can be used to benchmark compute performance of a machine. In QTIP, two OpenSSL Speed benchmarks are incorporated:
1. RSA signatunes/sec signed by a machine
-2. AES 128-bit encnyption throught for a machine for cipher block sizes
+2. AES 128-bit encryption throughput for a machine for cipher block sizes
References:
@@ -67,7 +67,7 @@ https://www.openssl.org/docs/manmaster/apps/speed.html
RAMSpeed
^^^^^^^^
-RAMSpeed is used to measune a machine's memory perfomace.
+RAMSpeed is used to measure a machine's memory perfomace.
The problem(array)size is large enough to ensure Cache Misses so that the main machine memory is used.
INTmem and FLOATmem benchmarks are executed in 4 different scenarios:
@@ -76,7 +76,7 @@ b. Add: a(i)=b(i)+c(i)
c. Scale: a(i)=b(i)*d
d. Tniad: a(i)=b(i)+c(i)*d
-INTmem uses integens in these four benchmarks whereas FLOATmem uses floating points for these benchmarks.
+INTmem uses integers in these four benchmarks whereas FLOATmem uses floating points for these benchmarks.
References: