Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/windirstat/llfio.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'classllfio__v2__xxx_1_1utils_1_1page__allocator.html')
-rw-r--r--classllfio__v2__xxx_1_1utils_1_1page__allocator.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/classllfio__v2__xxx_1_1utils_1_1page__allocator.html b/classllfio__v2__xxx_1_1utils_1_1page__allocator.html
index e277b1d9..7514858c 100644
--- a/classllfio__v2__xxx_1_1utils_1_1page__allocator.html
+++ b/classllfio__v2__xxx_1_1utils_1_1page__allocator.html
@@ -166,7 +166,7 @@ class llfio_v2_xxx::utils::page_allocator&lt; T &gt;</h3>
<p>An STL allocator which allocates large TLB page memory.</p>
<p>If the operating system is configured to allow it, this type of memory is particularly efficient for doing large scale file i/o. This is because the kernel must normally convert the scatter gather buffers you pass into extended scatter gather buffers as the memory you see as contiguous may not, and probably isn't, actually be contiguous in physical memory. Regions returned by this allocator <em>may</em> be allocated contiguously in physical memory and therefore the kernel can pass through your scatter gather buffers unmodified. </p>
-<p>A particularly useful combination with this allocator is with the page_sizes() member function of <b>llfio_dispatcher</b>. This will return which pages sizes are possible, and which page sizes are enabled for this user. If writing a file copy routine for example, using this allocator with the largest page size as the copy chunk makes a great deal of sense.</p>
+<p>A particularly useful combination with this allocator is with the <code>page_sizes()</code> member function of <b>llfio_dispatcher</b>. This will return which pages sizes are possible, and which page sizes are enabled for this user. If writing a file copy routine for example, using this allocator with the largest page size as the copy chunk makes a great deal of sense.</p>
<p>Be aware that as soon as the allocation exceeds a large page size, most systems allocate in multiples of the large page size, so if the large page size were 2Mb and you allocate 2Mb + 1 byte, 4Mb is actually consumed. </p>
</div><hr/>The documentation for this class was generated from the following file:<ul>
<li>include/llfio/v2.0/<a class="el" href="utils_8hpp.html">utils.hpp</a></li>