From: Alex Shi <alex.shi@intel.com>
To: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
arnd@arndb.de, rostedt@goodmis.org, fweisbec@gmail.com
Cc: jeremy@goop.org, alex.shi@intel.com, luto@mit.edu,
yinghai@kernel.org, riel@redhat.com, avi@redhat.com,
len.brown@intel.com, tj@kernel.org, akpm@linux-foundation.org,
cl@gentwo.org, borislav.petkov@amd.com, ak@linux.intel.com,
jbeulich@suse.com, eric.dumazet@gmail.com,
akinobu.mita@gmail.com, vapier@gentoo.org, cpw@sgi.com,
steiner@sgi.com, viro@zeniv.linux.org.uk,
kamezawa.hiroyu@jp.fujitsu.com, rientjes@google.com,
aarcange@redhat.com, linux-kernel@vger.kernel.org,
yongjie.ren@intel.com
Subject: [PATCH v9 0/9] x86 tlb optimisation and clean up
Date: Mon, 25 Jun 2012 14:08:18 +0800 [thread overview]
Message-ID: <1340604507-11214-1-git-send-email-alex.shi@intel.com> (raw)
Update to V9 version. This version is mainly for commit change.
1, It split the 6th patch into 6th and 7th for one patch to one issue.
2, update commit log for the 7th patch to include Yongjie's testing
results, I don't know why lkml can not show the e-mail, maybe some
words make it looks as spam?, Anyway I believe guys in to/cc list
have the data. So, attached the e-mail contents into log.
3, change commit log for 8th, 9th to include most clear explaination
and detailed testing result.
This patch set has clear performance gain, and clean up IDT table.
It is also quite safe after many review comments from Peter Anvin,
PeterZ, Nick Piggin, Steven Rostedt, Andi Kleen and Borislav etc.
And it runs well with my long time performance testing...
Anyone like to give the reason if it is not readly for upstream?
Best Regards!
Alex
[PATCH v9 1/9] x86/tlb_info: get last level TLB entry number of CPU
[PATCH v9 2/9] x86/flush_tlb: try flush_tlb_single one by one in
[PATCH v9 3/9] x86/tlb: fall back to flush all when meet a THP large
[PATCH v9 4/9] x86/tlb: add tlb_flushall_shift for specific CPU
[PATCH v9 5/9] x86/tlb: add tlb_flushall_shift knob into debugfs
[PATCH v9 6/9] mm/mmu_gather: enable tlb flush range in generic
[PATCH v9 7/9] x86/tlb: enable tlb flush range support for x86
[PATCH v9 8/9] x86/tlb: replace INVALIDATE_TLB_VECTOR by
[PATCH v9 9/9] x86/tlb: do flush_tlb_kernel_range by 'invlpg'
next reply other threads:[~2012-06-25 6:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 6:08 Alex Shi [this message]
2012-06-25 6:08 ` [PATCH v9 1/9] x86/tlb_info: get last level TLB entry number of CPU Alex Shi
2012-06-26 15:13 ` [tip:x86/mm] " tip-bot for Alex Shi
2012-06-25 6:08 ` [PATCH v9 2/9] x86/flush_tlb: try flush_tlb_single one by one in flush_tlb_range Alex Shi
2012-06-26 15:13 ` [tip:x86/mm] " tip-bot for Alex Shi
2012-06-25 6:08 ` [PATCH v9 3/9] x86/tlb: fall back to flush all when meet a THP large page Alex Shi
2012-06-26 15:14 ` [tip:x86/mm] " tip-bot for Alex Shi
2012-06-25 6:08 ` [PATCH v9 4/9] x86/tlb: add tlb_flushall_shift for specific CPU Alex Shi
2012-06-26 15:15 ` [tip:x86/mm] " tip-bot for Alex Shi
2012-06-25 6:08 ` [PATCH v9 5/9] x86/tlb: add tlb_flushall_shift knob into debugfs Alex Shi
2012-06-26 15:16 ` [tip:x86/mm] " tip-bot for Alex Shi
2012-06-25 6:08 ` [PATCH v9 6/9] mm/mmu_gather: enable tlb flush range in generic mmu_gather Alex Shi
2012-06-26 15:17 ` [tip:x86/mm] " tip-bot for Alex Shi
2012-06-25 6:08 ` [PATCH v9 7/9] x86/tlb: enable tlb flush range support for x86 Alex Shi
2012-06-26 15:18 ` [tip:x86/mm] " tip-bot for Alex Shi
2012-06-25 6:08 ` [PATCH v9 8/9] x86/tlb: replace INVALIDATE_TLB_VECTOR by CALL_FUNCTION_VECTOR Alex Shi
2012-06-26 15:19 ` [tip:x86/mm] " tip-bot for Alex Shi
2012-06-25 6:08 ` [PATCH v9 9/9] x86/tlb: do flush_tlb_kernel_range by 'invlpg' Alex Shi
2012-06-26 15:19 ` [tip:x86/mm] " tip-bot for Alex Shi
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=1340604507-11214-1-git-send-email-alex.shi@intel.com \
--to=alex.shi@intel.com \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=avi@redhat.com \
--cc=borislav.petkov@amd.com \
--cc=cl@gentwo.org \
--cc=cpw@sgi.com \
--cc=eric.dumazet@gmail.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jbeulich@suse.com \
--cc=jeremy@goop.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
--cc=mingo@redhat.com \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=vapier@gentoo.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yinghai@kernel.org \
--cc=yongjie.ren@intel.com \
/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
all inboxes | Powered by JetHome®