On Friday 05 January 2001 16:02, you wrote:
> Luis Chardon <[EMAIL PROTECTED]> wrote:
> > Yeah, that might be it. Is there a way to flush it besides "sync"?
> >
> > Here is the output:
> >
> > total used free shared buffers cached
> > Mem: 687708 489396 198312 0 198588 139984
> > -/+ buffers/cache: 150824 536884
> > Swap: 401584 0 401584
> >
> > Call me paranoid but I don't like seing around 200M in buffers :)
That's windows thinking. Linux doesn't like to see free memory. Unused
memory is wasted memory, not available resources. And most of the buffers
are read.
Write buffers are not usually First-In First-Out. There is a little
intelligence in the filesystem that performs writes to physically close areas
of the disk at about the same time, even if some scattered ones are delayed
to the next available cycle, but you are likely to find most of the memory in
use at all times. Also, some buffers are just areas of memory temporarily
reserved for that purpose until some running program needs more space and
requests it with malloc().
Civileme
