linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Michael Buesch <mbuesch@freenet.de>, Linux-MM@kvack.org
Subject: Re: find_vma() cachehit rate
Date: Tue, 23 Nov 2004 11:01:02 -0200	[thread overview]
Message-ID: <20041123130102.GA5268@logos.cnet> (raw)
In-Reply-To: <41A190D5.5060404@yahoo.com.au>

On Mon, Nov 22, 2004 at 06:10:13PM +1100, Nick Piggin wrote:
> Michael Buesch wrote:
> >Hi,
> >
> >I just saw this comment in find_vma():
> >  /* Check the cache first. */
> >  /* (Cache hit rate is typically around 35%.) */
> >
> >I just wanted to play around a bit. Just for fun.
> >So I wrote the attached patch to collect find_vma()
> >statistics. I was wondering why my cache hit rate is around
> >60%. It's always between 55 and 65 percent. Depending on
> >the workload.
> >Is this on obsolete comment from the 2.4 days, maybe?
> >
> >mb@lfs:~$ cat /proc/findvma_stat 
> >findvma_stat_cachehit  == 356524
> >findvma_stat_cachemiss == 248728
> >findvma_stat_fail      == 0
> >cachehit percentage    == 58%
> >cachemiss percentage   == 41%
> >fail percentage        == 0%
> >
> >My kernel is:
> >mb@lfs:~$ uname -r
> >2.6.10-rc2-ck2-nozeroram-findvmastat
> >
> >If you are interrested to comment on this, please CC: me,
> >as I'm not subscribed to this mailing list. Thanks.
> >
> 
> I think the cache hit rate will be pretty variable depending on the
> workload. For example, anything making use of threads, especially on
> an SMP system has the potential to decrease the cache's performance.
> 
> I wouldn't worry too much about the comment - it isn't really
> misleading, at worst inaccurate in a harmless sort of way. Basically
> it is there to say "hey, this really does help", I guess.

BTW, would be interesting to be able to use the PMC (performance counters) 
driver from mikpe to precisely measure cache hit ratio all over the kernel.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

      reply	other threads:[~2004-11-23 13:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-21  9:54 Michael Buesch
2004-11-22  7:10 ` Nick Piggin
2004-11-23 13:01   ` Marcelo Tosatti [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041123130102.GA5268@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=Linux-MM@kvack.org \
    --cc=mbuesch@freenet.de \
    --cc=nickpiggin@yahoo.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox