On Aug 11, 2016, at 3:19 PM, Scott Robison <sc...@casaderobison.com> wrote: > > I think you guys are just talking past each other.
Well, at least one of us isn’t communicating clearly, that’s certain. I just don’t yet know if it’s me, him, or both of us. :) > Windows versions that > support PAE have the Address Windowing Extensions (AWE) which allows a > single process to access more than 4 GiB total in a single process From what I can see, AWE and PAE are orthogonal, but AWE without PAE doesn’t let you get beyond 4 GiB in a single process on IA-32. But — and this may be where Keith was trying to go — a 32-bit app running on a 64-bit OS doesn’t need PAE because the host system does support more than 4 GiB of virtual memory. I have yet to see anything that says that AWE on 64-bit Windows couldn’t give a 32-bit app access to some of the VM beyond 4 GiB, even on consumer versions of Windows. If so, that’s what I was trying to get at with my request that he give a reference to the specific technology he’s talking about, instead of describing it in prose. > That being said, I don't think it is a reasonable or practical thing to > expect of cross platform source code like SQLite to use such a platform > specific API. Couldn’t it be abstracted behind a layer that used mmap() + tmpfs to pull off a similar trick on other 64-bit OSes? (I’m not talking about > 4 GiB on 32-bit OSes here.) It’d be a lot of work just to avoid rebuilding for 64-bit, but maybe it would be an interesting project for someone. Like a master’s university project, maybe. Still, it looks like we’re on the cusp of all the major OSes moving to 64-bit-only, so a lot of work made here might be obsolete soon. OS X and RHEL have already made the leap. Ubuntu and Microsoft both threatened to do this recently, but both backed down after user outcry. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
