Dan Hatton dan.hatton@btinternet.com writes:
The trouble is, I've gone about as far as I can with this efficiency drive, and in a couple of weeks, I have to do the same thing, with even bigger data sets. Since I have plenty of physical space (1GB RAM+10GB swap,) I'd like to get the kernel to allocate more to my program. I know there are various patches with names involving "HIGHMEM." My current kernel is 2.6.6, with
# CONFIG_NOHIGHMEM is not set CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set CONFIG_HIGHMEM=y
Would setting CONFIG_HIGHMEM64G=y and recompiling the kernel help me, or do I need to do something tricksier, please?
By my reading CONFIG_HIGHMEM64G is to support systems with lots of physical RAM, not to expand the process address space (which in any case go beyond 4GB on a 32-bit platform).
Time to buy an amd64 system, or figure out a less address-space-intensive way to do your block transfer computations.