Re:Memory and C++ Debugging at Electronic Arts [video]
by MaulingMonkey on Thursday October 08, 2015 @04:14AM
(#10351452)
> Since a each process gets its own entire 4GB virtual address space
2GB of which is reserved for kernel shenanigans unless everyone enabled /3GB in their kernel boot parameters (they haven't.)
Default allocators start failing at around half that amount.
Meanwhile I'm running out of memory on the new generation of consoles where I have 5GB of physical memory and no virtual memory fragmentation to worry about.
Re:Memory and C++ Debugging at Electronic Arts [video]
by danjayh on Thursday October 08, 2015 @11:20PM
(#10357968)
Truth on the kernel. I'm used to working in an environment where we own the OS, the board design, and the design of many of the chips ... which means we can make it do whatever we need (downside is, you have to maintain it all too). However, our needs are unique enough to justify it -- computing is hard in an environment where atmospheric radiation can flip random bits for you (See: https://en.wikipedia.org/wiki/Single_event_upset).
This is also why I suspect that they were mapping their virtual address space using block translation instead of a page table - if they had a page table, even in one process, it shouldn't have been a big issue since the virtual address space is many times larger than the available physical ram on the 360/PS3/Wii. The other possibility is that much of their RAM needs to be accessible by the GPU, for which fragmentation is an issue.