From: Shaohua Li <shaohua.li@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@elte.hu" <mingo@elte.hu>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>
Subject: Re: [tip:x86/mm] x86/mm: Avoid superflous leave_mm() in the TLB flush path
Date: Tue, 06 Dec 2011 08:40:20 +0800 [thread overview]
Message-ID: <1323132020.22361.364.camel@sli10-conroe> (raw)
In-Reply-To: <CA+55aFwMfUduX_5kNKjo=S8ShEBb_OE_D6o-jSMy53Sa0iZHAw@mail.gmail.com>
On Tue, 2011-12-06 at 07:26 +0800, Linus Torvalds wrote:
> On Mon, Dec 5, 2011 at 9:56 AM, tip-bot for Shaohua Li
> <shaohua.li@intel.com> wrote:
> >
> > x86/mm: Avoid superflous leave_mm() in the TLB flush path
> >
> > If just one page VA tlb is required to be flushed and current
> > task is in lazy TLB state, doing leave_mm() is superfluous
> > because it flushes the whole TLB. This can reduce some TLB
> > miss.
>
> Are you sure this is a good idea?
>
> We may be *much* better off leaving the VM and avoiding future IPI's
> than trying to flush pages one by one over and over again.
>
> IPI's are expensive.
>
> I don't think you thought this through, and if you *did* think it
> through and actually have numbers that it's cheaper to stay with the
> MM, I think you need to show those numbers.
good point, I didn't think of it. It's unlikely we just flush one tlb
page. please drop the patch.
Thanks,
Shaohua
next prev parent reply other threads:[~2011-12-06 0:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-287de5b2cb365b98190b5de8ace1c5a31768a5ae@git.kernel.org>
2011-12-05 23:26 ` Linus Torvalds
2011-12-06 0:40 ` Shaohua Li [this message]
2011-12-06 5:31 ` Ingo Molnar
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=1323132020.22361.364.camel@sli10-conroe \
--to=shaohua.li@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®