> On Wednesday 23 May 2001 03:09, you wrote:
> > This does not equate to a memory leak, there is no point in removing file
> > data from the cache unless there is another use for the memory, there is
> > always the possibility that it might be used again. All these numbers
> > mean is the memory has file data in it (it will be clean).
> I booted my system this morning. During the day, it did not much
> else than light mail trafic. At 3 pm I noticed from the unresponsivness
> of the system that not everything was quite the same as in the
> morning. Memory usage 200MB, free 56. Quite large numbers for
> xfs_inode and inode_cache in /proc/slabinfo.
The inode pool sizes are what the latest fixes should help with.
> It runs a cvs copy from May 22 11.00 AM, EST (8 PM GMT).
> I would try a later copy if cvs server let me check it out but
> cvs update -d does not work any longer as it used to.
Hmm this appears to be working now - at least from here.
> > I also checked in a change today which will change memory usage when under
> > pressure - which this system is not.