Re: [coLinux-devel] a. Memory leak ?, b. number of /dev/cobd?

[Dan A. <da...@co...>]

On Wed, Apr 14, 2004 at 06:53:01PM +0800, Eugene Teo wrote:
> <quote sender="Dan Aloni">
> > On Wed, Apr 14, 2004 at 11:52:21AM +0200, Axel Jessner wrote:
> > > Hello everyone,
> > > 
> > > I am finding coLinux allready an extremely useful and productive way to help me use the best of both the Linux and
> > > Win-world. I am running it on a WIN2K Laptop (1 GB RAM and 2 GHz clock) where both are stable. 
> > > 
> > > Problem a.
> > > I made an overnight test using my own software to create an index of several 10k binary raw data files residing in roughly two
> > > hundred directories on an external 160 GB USB masstorage  drive. This meant finding, opening reading each file and writing some
> > > catalogue information to a text file.
> > > All in all this were  about 90 GB of data. The programme started to execute  quickly and efficiently but in the next morning it
> > > had ground to slow crawl. I found that everthing was swapped out and and swap-use continued to increase.
> > 
> > Did you rule out the possiblity that your userspace program has a leak,
> > and not the kernel? Unless you see lines such as '__alloc_pages: 0-order 
> > allocation failed', chances are there was no kernel memory leak. 
> > The symptoms you describe fit more to the case where a userspace 
> > program eats up too much memory.
> 
> even if you get to see such lines '__alloc_pages: 0-order allocation
> failed', it does not mean that there is a kernel memory leak. That could
> mean that the memory is trying really hard to accomodate and allocate
> memory under a really bad pressure.

The situation you are describing is more likely to occur when no
swap is installed, but that's not the case here.
 
-- 
Dan Aloni
da...@co...