![]() | ||||||||||
Messages in this thread |
Con Kolivas wrote: > > On Tuesday 31 Dec 2002 5:08 pm, Andrew Morton wrote: > > Con Kolivas wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA1 > > > > > > On Saturday 28 Dec 2002 5:16 pm, Con Kolivas wrote: > > > > Is there something about the filesystem layer or elsewhere in the > > > > kernel that could decay or fragment over time that only a reboot can > > > > fix? This would seem to be a bad thing. > > > > > > Ok Linus suggested I check slabinfo before and after. > > > > > > I ran contest for a few days till I recreated the problem and it did > > > recur. I don't know how to interpret the information so I'll just dump it > > > here: > > > > Looks OK. Could we see /proc/meminfo and /proc/vmstat? > > meminfo: > MemTotal: 257296 kB > MemFree: 47468 kB > Buffers: 27028 kB > Cached: 7480 kB > SwapCached: 272 kB > Active: 154968 kB > Inactive: 42756 kB > HighTotal: 0 kB > HighFree: 0 kB > LowTotal: 257296 kB > LowFree: 47468 kB > SwapTotal: 4194272 kB > SwapFree: 4193816 kB > Dirty: 1116 kB > Writeback: 0 kB > Mapped: 3740 kB > Slab: 8564 kB > Committed_AS: 6580 kB > PageTables: 196 kB > ReverseMaps: 1381 > These numbers _look_ wrong, but ext3 truncate does funny things. Could you now run a big usemem/fillmem application to try to allocate and use 200 megs of memory, then resend /proc/meminfo? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2005-03-22 11:32 [W:0.172 / U:0.030 seconds] ©2003-2008 Jasper Spaans | ||||||||||