VeraCrypt
aboutsummaryrefslogtreecommitdiff
path: root/doc/html/Pipelining.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/Pipelining.html')
-rw-r--r--doc/html/Pipelining.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/html/Pipelining.html b/doc/html/Pipelining.html
index f50655d2..eb1834fe 100644
--- a/doc/html/Pipelining.html
+++ b/doc/html/Pipelining.html
@@ -10,8 +10,8 @@
</head>
<body>
-<div>
-<a href="https://www.veracrypt.fr/en/Home.html"><img src="VeraCrypt128x128.png" alt="VeraCrypt"/></a>
+<div>
+<a href="Documentation.html"><img src="VeraCrypt128x128.png" alt="VeraCrypt"/></a>
</div>
<div id="menu">
@@ -27,7 +27,7 @@
<div>
<p>
-<a href="Documentation.html">Documentation</a>
+<a href="Documentation.html">Documentation</a>
<img src="arrow_right.gif" alt=">>" style="margin-top: 5px">
<a href="Pipelining.html">Pipelining</a>
</p></div>
@@ -48,4 +48,4 @@ Note: Pipelining is implemented only in the Windows versions of VeraCrypt.</div>
<p><span style="text-align:left; font-size:10px; line-height:12px">* Some solid-state drives compress data internally, which appears to increase the actual read/write speed when the data is compressible (for example, text files). However, encrypted data cannot
be compressed (as it appears to consist solely of random &quot;noise&quot; without any compressible patterns). This may have various implications. For example, benchmarking software that reads or writes compressible data (such as sequences of zeroes) will report lower
speeds on encrypted volumes than on unencrypted volumes (to avoid this, use benchmarking software that reads/writes random or other kinds of uncompressible data)</span><span style="text-align:left; font-size:10px; line-height:12px">.</span></p>
-</div><div class="ClearBoth"></div></body></html> \ No newline at end of file
+</div><div class="ClearBoth"></div></body></html>