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

[Eugene T. <eug...@eu...>]

<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.

It is interesting to see such behaviour though. I would suggest Axel do a
simpler test to see if it is indeed your userspace application that is
causing this problem.

Eugene
-- 
Eugene TEO -  <eugeneteo%null!cc!uic!edu> <http://www.anomalistic.org/>
1024D/14A0DDE5 print D851 4574 E357 469C D308  A01E 7321 A38A 14A0 DDE5
main(i) { putchar(182623909 >> (i-1) * 5&31|!!(i<7)<<6) && main(++i); }