> Exclusion or inclusion of NR_MLOCK number is straightforward for the dirty > ratio calcuations. global_page_state(NR_MLOCK) f.e. would get us totals on > mlocked pages per zone. node_page_state(NR_MLOCK) gives a node specific > number of mlocked pages. The nice thing about ZVCs is that it allows > easy access to counts on different levels.
however... mlocked pages still can be dirty, and want to be written back at some point ;) I can see the point of doing dirty ratio as percentage of the LRU size, but in that case you don't need to track NR_MLOCK, only the total LRU size. (And yes it'll be sometimes optimistic because not all mlock'd pages are moved off the lru yet, but I doubt you'll have that as a problem in practice) -- if you want to mail me at work (you don't), use arjan (at) linux.intel.com Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
