Greg Lindahl wrote:
> > This is related to my previous question about direct I/O. If my
> > program has a huge memory requirement, I would prefer to use up as much
> > system memory as is available, thus reducing swapping action.
> Right. Like most modern Unix implementations, Linux will use all of memory
> for disk caching depending on system activity. The traditional way to
> represent this in Unix is to mmap the entire file. This works in Linux just
> like everywhere else. All filesystems support mmap.
Correct me if I'm wrong, but I interpreted the question as:
Is there a way to prevent the disk/file cache from displacing memory used by
processes, so the process data stay in memory and don't get swapped out?
Here's the original question, note the last two sentences in particular (which
you didn't quote):
Eugene Chu wrote:
> Thanks for the reply Greg.
> This is related to my previous question about direct I/O. If my
> program has a huge memory requirement, I would prefer to use up as much
> system memory as is available, thus reducing swapping action. Now, if
> the program needs to read and write a lot of files in the process, I
> have another user of memory; file system caching. I don't know how it
> works in Linux, but unified buffer caching usually means that the
> system uses up all available memory for file caching. So I either need
> more memory or a file I/O method that bypasses system caching. Would
> the various file systems types available in Linux be able to provide
> this capability?
Axp-list mailing list
This archive was generated by hypermail version 2a22 on Fri Sep 1 05:03:57 2000 PDT
Send any problems or questions about this archive to email@example.com.