<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On Nov 13, 2018, at 1:23 PM, Stefan Dösinger <<a href="mailto:stefandoesinger@gmail.com" class="">stefandoesinger@gmail.com</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Am 13.11.2018 um 19:46 schrieb Axel Davy <<a href="mailto:davyaxel0@gmail.com" class="">davyaxel0@gmail.com</a>>:<br class=""><div class=""><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class=""><p class="">I assume on windows, OpenGL, d3d, etc all allocate in the 2GB.
Thus I believe most of the difference is the space taken by the
mapped library codes (llvm, libx11, etc), and eventually some
libraries allocating more space than they should (pulseaudio).</p></div></div></blockquote><div class="">As far as I understand on Vista and later D3DPOOL_DEFAULT resources don't consume client address space as long as they stay in GPU memory. When they get paged out of the GPU, they reside in the app's address space.</div></div></div></div></blockquote><br class=""></div><div>Hmm, really? What would happen if there isn't room in the process address space at that point?</div><br class=""><div class="">-Ken</div><div class=""><br class=""></div></body></html>