Q: too much data too little memory

From: Fei Chen (feic@stats.ox.ac.uk)
Date: 04/17/03


From: Fei Chen <feic@stats.ox.ac.uk>
Date: Thu, 17 Apr 2003 13:30:16 +0100

Dear all,

Advanced appologies if this turns out to be a trivial question.

I was wondering, with a large chunk of data that does not fit into all the
physical memory available to a computer, is it better, to run one process
that attempts to load all the data, and thus off loading the memory
management work to the OS (e.g. via paging/swapping). Or is it better to
start several processes concurrently, each of which takes in a chunk of
data that individually does fit into memory, and thus have the OS manage
these processes. Or there is really little difference between these two
approaches?

Thanks for any pointers,

Fei Chen



Relevant Pages

  • Re: [Vuln-Dev Challenge] - VulnDev1.c Summary
    ... meaning the chunk is allocated with mmap. ... turn calls munmap on an invalid memory address. ... > the Doug Lea algorithm as well has heap-based exploitation methods ... > the forward chunk, in our case buf2, is free. ...
    (Vuln-Dev)
  • The Malloc Maleficarum
    ... Glibc Malloc Exploitation Techniques ... the exploitation of overflowed dynamic memory chunks on Linux. ... I have the House of Prime. ... a malloc chunk. ...
    (Bugtraq)
  • [Full-disclosure] The Malloc Maleficarum
    ... Glibc Malloc Exploitation Techniques ... the exploitation of overflowed dynamic memory chunks on Linux. ... I have the House of Prime. ... a malloc chunk. ...
    (Full-Disclosure)
  • Re: My idea of fully-portable C code
    ... claimed that I write fully-portable code. ... In my most recent embedded project, there was a severe memory ... chunk size bigger or smaller than 3 bits). ... } ChunkAddress; ...
    (comp.arch.embedded)
  • Re: [RFC v11][PATCH 05/13] Dump memory address space
    ... in one or more chunk: each chunk begins with a header that specifies ... should not change in the interim anyways, the locks protects us from, e.g. ... Even scanning over a large amount of memory, you aren't going to see a performance difference for accessing pgarr from an argument vs off of field in ctx which is going to be cache-hot. ... It is strictly necessary when it comes to handling shared memory. ...
    (Linux-Kernel)

Loading