From: Rik van Riel <riel@redhat.com>
To: Alex Shi <alex.shi@intel.com>
Cc: andi.kleen@intel.com, tim.c.chen@linux.intel.com,
jeremy@goop.org, chrisw@sous-sol.org, akataria@vmware.com,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
rostedt@goodmis.org, fweisbec@gmail.com, luto@mit.edu,
avi@redhat.com, len.brown@intel.com,
paul.gortmaker@windriver.com, dhowells@redhat.com,
fenghua.yu@intel.com, borislav.petkov@amd.com,
yinghai@kernel.org, cpw@sgi.com, steiner@sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] x86/tlb_info: get last level TLB entry number of CPU
Date: Wed, 02 May 2012 11:13:23 -0400 [thread overview]
Message-ID: <4FA14F13.6040002@redhat.com> (raw)
In-Reply-To: <1335603006-2572-2-git-send-email-alex.shi@intel.com>
On 04/28/2012 04:50 AM, Alex Shi wrote:
> For 4KB pages, x86 CPU has 2 or 1 level TLB, first level is data TLB and
> instruction TLB, second level is shared TLB for both data and instructions.
>
> For hupe page TLB, usually there is just one level and seperated by 2MB/4MB
> and 1GB.
>
> Although each levels TLB size is important for performance tuning, but for
> genernal and rude optimizing, just last level TLB entry number is suitable.
> And in fact, last level TLB has the biggest entry number.
>
> This patch will get the biggest TLB entry number and use it in furture TLB
> optimizing.
>
> Signed-off-by: Alex Shi<alex.shi@intel.com>
Acked-by: Rik van Riel <riel@redhat.com>
next prev parent reply other threads:[~2012-05-02 15:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-28 8:50 [PATCH 1/3] x86/tlb_info: get last level TLB entry number of CPU Alex Shi
2012-04-28 8:50 ` [PATCH 2/3] x86/flush_tlb: try flush_tlb_single one by one in flush_tlb_range Alex Shi
2012-05-02 15:21 ` Rik van Riel
2012-05-02 15:13 ` Rik van Riel [this message]
2012-04-28 8:51 [PATCH 0/3] TLB flush range optimization Alex Shi
2012-04-28 8:51 ` [PATCH 1/3] x86/tlb_info: get last level TLB entry number of CPU Alex Shi
2012-04-29 13:55 ` Borislav Petkov
2012-04-30 4:25 ` Alex Shi
2012-04-30 10:45 ` Borislav Petkov
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=4FA14F13.6040002@redhat.com \
--to=riel@redhat.com \
--cc=akataria@vmware.com \
--cc=alex.shi@intel.com \
--cc=andi.kleen@intel.com \
--cc=avi@redhat.com \
--cc=borislav.petkov@amd.com \
--cc=chrisw@sous-sol.org \
--cc=cpw@sgi.com \
--cc=dhowells@redhat.com \
--cc=fenghua.yu@intel.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
--cc=mingo@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=rostedt@goodmis.org \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=yinghai@kernel.org \
/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.