> > * Liu Yuan <namei.unix@xxxxxxxxx> wrote: > > > + if (likely(!retry_find) && page && PageUptodate(page)) > > + page_cache_acct_hit(inode->i_sb, READ); > > + else > > + page_cache_acct_missed(inode->i_sb, READ); > > Sigh. > > This would make such a nice tracepoint or sw perf event. It could be collected in a > 'count' form, equivalent to the stats you are aiming for here, or it could even be > traced, if someone is interested in such details. > > It could be mixed with other events, enriching multiple apps at once. Totally agreed. > But, instead of trying to improve those aspects of our existing instrumentation > frameworks, mm/* is gradually growing its own special instrumentation hacks, missing > the big picture and fragmenting the instrumentation space some more. > > That trend is somewhat sad. So, I think thing is, the stat is how much people and how frequently used. If it is really really really common, /proc/meminfo or similar special place is good idea. Another example, If the stat can help our MM debugging to handle LKML bug report, it is worth to have special care. But other almost else case are better to use generic framework. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>