On Wednesday 13 September 2006 12:05 pm, Jesse Off wrote:
> I really doubt you'll find anything interesting investigating our
> kernel modifications for sources of memory leaks. I just personally
> audited Cirrus' ethernet driver and found only 2 calls to "kmalloc"
> and those are only at driver initialization and total less than a
> few kilobytes. Anything that appears to "leak" relating to network
> function would have to be at untouched (by Cirrus or TS) 2.4.26
> areas of Linux kernel code.
That's good to know! I ran my 'test' for a short period using the rootfs on
flash and didn't see the problem. I'm working on a smarter, more definitive
test. Lots of variables to wade through...
> The VM system is somewhat unique on this processor since it uses a
> subsystem rarely used on Linux/x86 for handling discontiguous memory
> blocks. We've already found and fixed one bug in the original
> code. Its severity made me doubt the level of testing and quality
> of thought the 2.4.26 authors originally put into it, so I wouldn't
> be surprised if it has other quirks regarding memory usage
> reporting. If its actually responsible for leaking memory (which I
> still doubt), my feeling of general unease about quality will be
> replaced with outrage ;-) -- though really its kind of hard to get
> mad with something thats free and has no warranty. :-)
Also good to know. Thanks! I'll post again when I have something more
definitive to share.
Steve
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|