Re: Can 64 bit Vista support a 32 bit application with 4 GB?

"Jerome H. Fine" <spamtrap@xxxxxxxxxx> wrote:

In addition, there is a DLL program which I hope to use under the
emulator which also requests
memory. If I am able to make my own modifications to the DLL, I will be
using it to sieve for
prime numbers up around 10**18. If I can accomplish what I estimate is
possible, the DLL will
ask for as much virtual memory as possible (at least 1.5 GB) which must
be physical memory
NOT backed up via a swap file or any other file if the sieve is going to
run at a reasonable speed.

It is THAT assumption that I challenge. You are simply assuming a priori
that the Windows XP kernel is too stupid to optimize its behavior for your
application. Unless your memory usage is pathological, I simply do not
automatically accept that your sieve will not run at a reasonable speed
using standard paging.


I seem to remember that there was a similar situation with respect to
the STAR-100
(from CDC) operating system back in 1972. That was also a virtual
operating system
with a 256 TeraByte virtual address space with a 48 bit address. I tend
to remember
that several programs trashed themselves to death when their working set
exceeded
physical memory - which back then was only a few MegaBytes. I wrote the
part
of the operating system which handled the paging and wrote the LRU
(least recently
used) pages out to the swap file. The size of large pages was 65536
bytes, so there
were not very many large pages available.

Interesting that you worked on the Star-100. I spent the 1980s working for
Control Data, and I got the job in part based on an interview at Oregon
State with a guy from the Star-100 team. He and I talked shop for the
whole hour, then he said "Tell you what, I'll just write down what they
want to hear." It must have worked.
--
Tim Roberts, timr@xxxxxxxxx
Providenza & Boekelheide, Inc.

.

Relevant Pages

  • Re: Why do we need executables in certain formats ?
    ... > complex binary formats was that programs need to be relocated, ... > perhaps linked with libraries. ... Modern virtual memory processors can locate to ... > has a hidden problem with the new .DLL. ...
    (comp.lang.asm.x86)
  • Re: Why is Base3.exe using 700+ K in windows task manager ?
    ... DLL function. ... handles opened by any thread of the calling process ... The DLL allocates memory from the virtual address space of the calling ... Who can tell where memory is really located in a virtual adress space? ...
    (alt.lang.asm)
  • Re: shared DLL VS static Link, Are they different?
    ... MFC exits, and if there is any memory that is freed at that time, MFC will ... business dumping leaks; it should wait until the CRT DLL dumps leaks after ... ALL RESOURCES OWNED BY THAT PROCESS ARE RELEASED. ...
    (microsoft.public.vc.mfc)
  • Re: Linking to a .NET dll from C#
    ... for obtaining price quotes and performance is absolutely critical. ... be to use shared memory or memory mapped files. ... Be aware that in these scenarios you're responsible for patching and updates, as the application will no longer rely on the clients machine to keep the framework up to date. ... Determine if a certain managed .NET dll or assembly is loaded ...
    (microsoft.public.dotnet.general)
  • Re: Memory Management Tools
    ... Memory limits in 32 Bit world. ... There is still a fairly high risk in moving ... One area where real optimization actually is possible is DLL rebasing. ... Well, the Windows loader, which loads the DLL into memory (which in ...
    (microsoft.public.windows.terminal_services)