First indications are that it does. I have been tarring over nfs to
/dev/null. But I was doing that before too.
Mem-info:
Free pages: 1736kB
( 28*4kB 85*8kB 17*16kB 3*32kB 1*64kB 4*128kB = 1736kB)
Swap cache: add 15/15, delete 7280365/15, find 75/0
Free swap: 144492kB
16384 pages of RAM
448 free pages
619 reserved pages
6590 pages shared
Buffer memory: 18324kB
Buffer heads: 18344
Buffer blocks: 18324
CLEAN: 17784 buffers, 106 used (last=106), 0 locked, 0 protected, 0
dirty
LOCKED: 497 buffers, 56 used (last=487), 0 locked, 0 protected, 0
dirty
DIRTY: 9 buffers, 0 used (last=0), 0 locked, 0 protected, 9 dirty
Networking buffers in use : 12222
Network buffers locked by drivers : 0
Total network buffer allocations : 4759209
Total failed network buffer allocs : 0
Total free while locked events : 0
IP fragment buffer size : 0
> its a networking leak, if not its a somethign else leak
Memory use has gone down a bit. Somebody logged out.
ptb% free
total used free shared buffers cached
Mem: 63060 61316 1744 27068 18968 11604
-/+ buffers: 30744 32316
Swap: 144544 52 144492
> Alan
(2.0.33 compiled with 2.7.2).
It's way too early to say anything at the moment, though I am trying to
"age" this kernel as fast as I can. I decided not to apply the memleak
patch for the moment. I've copied the setup to another machine and am
trying to duplicate the behaviour there. No indications so far.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu