+- Sick Gaming (https://www.sickgaming.net)
+-- Forum: Computers (https://www.sickgaming.net/forum-86.html)
+--- Forum: Linux, FreeBSD, and Unix types (https://www.sickgaming.net/forum-88.html)
+--- Thread: Handling Complex Memory Situations (/thread-89565.html)
Handling Complex Memory Situations - xSicKxBot - 03-30-2019
Handling Complex Memory Situations
<div><div class="lcom-stacked__main">
<div class="panel-pane pane-entity-field pane-node-body">
<div class="field field-name-body field-type-text-with-summary field-label-hidden">
<div class="field-items">
<div class="field-item even">
<p><strong>Jérôme Glisse</strong> felt that the time had come for the Linux kernel to address seriously the issue of having many different types of memory installed on a single running system. There was main system memory and device-specific memory, and associated hierarchies regarding which memory to use at which time and under which circumstances. This complicated new situation, Jérôme said, was actually now the norm, and it should be treated as such.</p>
<p>The physical connections between the various CPUs and devices and RAM chips—that is, the bus topology—also was relevant, because it could influence the various speeds of each of those components.</p>
<p>Jérôme wanted to be clear that his proposal went beyond existing efforts to handle heterogeneous RAM. He wanted to take account of the wide range of hardware and its topological relationships to eek out the absolute highest performance from a given system.</p>
<p>Read more at <a href="https://www.linuxjournal.com/content/handling-complex-memory-situations">Linux Journal</a></p>
</div>
</div>
</div></div>
</p></div>
<p><a href="https://www.linux.com/popup/nojs" class="ctools-use-modal ctools-modal-subscription-modal-style element-invisible" title>Click Here!</a> </p>
</div>