All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: "CHADHA,VINEET" <vineet@ufl.edu>
Cc: nickpiggin@yahoo.com.au, linux-kernel@vger.kernel.org
Subject: Re: TLB evaluation for Linux
Date: Tue, 02 Sep 2008 08:31:28 +0200	[thread overview]
Message-ID: <87od37vz27.fsf@basil.nowhere.org> (raw)
In-Reply-To: <1942732773.182121220328723728.JavaMail.osg@osgjas04.cns.ufl.edu> (VINEET CHADHA's message of "Tue, 2 Sep 2008 00:12:03 -0400 (EDT)")

"CHADHA,VINEET" <vineet@ufl.edu> writes:

> Hi,
>
> I have been working to evaluate TLB performance for Linux O/S and
> virtualized workloads(such as Xen) in a Full system
> simulator(e.g. simics). While my evaluation is in nascent stage, I do
> notice that most of the IPIs in multi-core environments cause complete
> TLB Flush.
>
> I want to evaluate cost of TLB shootdown including re-population
> vs. each entry shootdown (invlpg). While a similar study has been done
> in other kernels (e.g. L4 kernel), I am not aware if it has been done
> for Linux O/S.
>
> Are there hooks or patches to test or evaluate TLB
> performance. Specifically, I would like to know where to make changes
> in Linux kernel to support each entry shootdown.

Linux doesn't use a threshold to distingush between range flush
and full flush in certain situations, but always does the full
flush. 

That is something that might be possible to be improved, but it was so
far always unclear how much it helps (it depends on the particular TLB
size, cost of TLB refill etc.)

-Andi

-- 
ak@linux.intel.com

  parent reply	other threads:[~2008-09-02  6:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-02  4:12 TLB evaluation for Linux CHADHA,VINEET
2008-09-02  4:39 ` Nick Piggin
2008-09-02  6:31 ` Andi Kleen [this message]
2008-09-02 13:43 ` Arjan van de Ven
  -- strict thread matches above, loose matches on Subject: below --
2008-09-02 14:36 CHADHA,VINEET
2008-09-02 14:59 CHADHA,VINEET
2008-09-02 15:38 ` Arjan van de Ven
2008-09-02 16:14 CHADHA,VINEET

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=87od37vz27.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=vineet@ufl.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.