On Fri, 21 Sep 2012, Nico Schottelius wrote: > Active / Total Objects (% used) : 1165130 / 1198087 (97.2%) > Active / Total Slabs (% used) : 81027 / 81027 (100.0%) > Active / Total Caches (% used) : 69 / 101 (68.3%) > Active / Total Size (% used) : 1237249.81K / 1246521.94K (99.3%) > Minimum / Average / Maximum Object : 0.01K / 1.04K / 15.23K > > OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME > 993607 993607 100% 1.21K 75358 26 2411456K jfs_ip Well that doesn't look good. 100% of the inode cache for jfs are being used which either means - there's a memory leak, or - there's some sort of throttling issue in jfs. And those objects are consuming ~2.3GB of slab on your 4GB machine and seems to only have occurred between v3.4.2 to v3.5.3. It would be interesting to see what kmemleak would tell us. Adding Dave Kleikamp to the cc. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
