From: Andi Kleen <ak@suse.de>
To: Roberto Nibali <ratz@drugphish.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: TLB flush counters gone in 2.5.35-bk?
Date: 17 Sep 2002 18:59:07 +0200 [thread overview]
Message-ID: <p73znugtuw4.fsf@oldwotan.suse.de> (raw)
In-Reply-To: Roberto Nibali's message of "17 Sep 2002 17:44:57 +0200"
Roberto Nibali <ratz@drugphish.ch> writes:
> Why was that done? I'm actually about to conduct some tests where I
> think that I need this information to check the L1 <-> L2 caching size
> influence on kernel data structures. What is the problem with the
> existing counters, did I miss some discussion on LKML?
You can easily get the same information from the CPU performance counters
(e.g. via oprofile)
-Andi
next parent reply other threads:[~2002-09-17 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D874DA1.20803@drugphish.ch.suse.lists.linux.kernel>
2002-09-17 16:59 ` Andi Kleen [this message]
2002-09-17 18:45 ` TLB flush counters gone in 2.5.35-bk? Roberto Nibali
2002-09-17 15:43 Roberto Nibali
2002-09-17 20:55 ` Andrew Morton
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=p73znugtuw4.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ratz@drugphish.ch \
/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