<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - i915 kernel driver unable to initialize device (-28) ( Xeon E3-1275 v6 ) unless Aperture size <= 128MB"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107426#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - i915 kernel driver unable to initialize device (-28) ( Xeon E3-1275 v6 ) unless Aperture size <= 128MB"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107426">bug 107426</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>(In reply to Krist from <a href="show_bug.cgi?id=107426#c14">comment #14</a>)
<span class="quote">> Created <span class=""><a href="attachment.cgi?id=140891" name="attach_140891" title="256MB: lspci -vvv -s 0:0:2">attachment 140891</a> <a href="attachment.cgi?id=140891&action=edit" title="256MB: lspci -vvv -s 0:0:2">[details]</a></span>
> 256MB: lspci -vvv -s 0:0:2</span >
Ok, we are not going completely mad, your BIOS is buggy.
(In reply to Krist from <a href="show_bug.cgi?id=107426#c15">comment #15</a>)
<span class="quote">> The mappable limit of 128MB is affecting us, because we are trying to run 4
> different HD video encoders using the Intel Media SDK.
> For running all these video encoders, we are required to have numerous VA
> Surface buffers and we need more than 128MB of them.</span >
Mappable has no impact on the amount of usable memory. It impacts the number of
surfaces that can be directly mapped through the very slow indirect GTT. If
userspace is using that as it's preferred means of access, it needs to be
shouted at. Still, that is handled as 2MiB chunks, the size of surface and the
number of them have little impact, the size of the aperture basically means how
many concurrent access you can handle before thrashing forces eviction.
The biggest consume of mappable is the display engine, but even that can handle
unmmappable memory for the main part (some features like FBC not withstanding).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>