From: Ingo Molnar <mingo@elte.hu>
To: Frederik Deweerdt <frederik.deweerdt@xprog.eu>,
Tejun Heo <tj@kernel.org>
Cc: tglx@linutronix.de, ak@linux.intel.com, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [patch] x86_32: use 8 IPI vectors for tlb flush (as x86_64)
Date: Tue, 3 Feb 2009 06:45:59 +0100 [thread overview]
Message-ID: <20090203054559.GA20154@elte.hu> (raw)
In-Reply-To: <20090202235414.GA16750@gambetta>
* Frederik Deweerdt <frederik.deweerdt@xprog.eu> wrote:
> Hi,
>
> The following patch allows using 8 different IPI vectors on ia32 for tlb
> flushes, this reduces the contention on the tlbstate_lock. It also makes
> the 32 bits version closer to the 64 bits version.
This was done recently :-(
Are you aware of the x86 development tree? It's included in the -tip tree
and can be found at:
http://people.redhat.com/mingo/tip.git/README
Credit goes to Tejun Heo who unified the 32-bit and 64-bit TLB code (which
also means 32-bit uses the 8 IPI vectors) - the code is now all in
arch/x86/mm/tlb.c.
Ingo
prev parent reply other threads:[~2009-02-03 5:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 23:54 [patch] x86_32: use 8 IPI vectors for tlb flush (as x86_64) Frederik Deweerdt
2009-02-03 5:45 ` Ingo Molnar [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=20090203054559.GA20154@elte.hu \
--to=mingo@elte.hu \
--cc=ak@linux.intel.com \
--cc=frederik.deweerdt@xprog.eu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox