From: Dave Hansen <dave.hansen@intel.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>,
Andy Lutomirski <luto@amacapital.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>, Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org
Subject: Re: PCID and TLB flushes (was: [GIT PULL] kdbus for 4.1-rc1)
Date: Tue, 28 Apr 2015 15:38:00 -0700 [thread overview]
Message-ID: <55400BC8.6080204@intel.com> (raw)
In-Reply-To: <20150428221553.GA5770@node.dhcp.inet.fi>
On 04/28/2015 03:15 PM, Kirill A. Shutemov wrote:
> On Tue, Apr 28, 2015 at 01:42:10PM -0700, Andy Lutomirski wrote:
>> At some point, I'd like to implement PCID on x86 (if no one beats me
>> to it, and this is a low priority for me), which will allow us to skip
>> expensive TLB flushes while context switching. I have no idea whether
>> ARM can do something similar.
>
> I talked with Dave about implementing PCID and he thinks that it will be
> net loss. TLB entries will live longer and it means we would need to trigger
> more IPIs to flash them out when we have to. Cost of IPIs will be higher
> than benifit from hot TLB after context switch.
>
> Do you have different expectations?
Kirill, I think Andy is asking about something different that what you
and I talked about. My point to you was that PCIDs can not be used to
to replace or in lieu of TLB shootdowns because they *only* make TLB
entries live longer.
Their entire purpose is to make things live longer and to reduce the
cost of the implicit TLB shootdowns that we do as a part of a context
switch.
I'm not sure if it will have a benefit overall. It depends on the
increase in shootdown cost vs. the decrease in TLB refill cost at
context switch.
I think someone hacked up some code to do it (maybe just internally to
Intel), so if anyone is seriously interested in implementing it, let me
know and I'll see if I can dig it up.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave.hansen@intel.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>,
Andy Lutomirski <luto@amacapital.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>, Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org
Subject: Re: PCID and TLB flushes (was: [GIT PULL] kdbus for 4.1-rc1)
Date: Tue, 28 Apr 2015 15:38:00 -0700 [thread overview]
Message-ID: <55400BC8.6080204@intel.com> (raw)
In-Reply-To: <20150428221553.GA5770@node.dhcp.inet.fi>
On 04/28/2015 03:15 PM, Kirill A. Shutemov wrote:
> On Tue, Apr 28, 2015 at 01:42:10PM -0700, Andy Lutomirski wrote:
>> At some point, I'd like to implement PCID on x86 (if no one beats me
>> to it, and this is a low priority for me), which will allow us to skip
>> expensive TLB flushes while context switching. I have no idea whether
>> ARM can do something similar.
>
> I talked with Dave about implementing PCID and he thinks that it will be
> net loss. TLB entries will live longer and it means we would need to trigger
> more IPIs to flash them out when we have to. Cost of IPIs will be higher
> than benifit from hot TLB after context switch.
>
> Do you have different expectations?
Kirill, I think Andy is asking about something different that what you
and I talked about. My point to you was that PCIDs can not be used to
to replace or in lieu of TLB shootdowns because they *only* make TLB
entries live longer.
Their entire purpose is to make things live longer and to reduce the
cost of the implicit TLB shootdowns that we do as a part of a context
switch.
I'm not sure if it will have a benefit overall. It depends on the
increase in shootdown cost vs. the decrease in TLB refill cost at
context switch.
I think someone hacked up some code to do it (maybe just internally to
Intel), so if anyone is seriously interested in implementing it, let me
know and I'll see if I can dig it up.
next prev parent reply other threads:[~2015-04-28 22:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 22:15 PCID and TLB flushes (was: [GIT PULL] kdbus for 4.1-rc1) Kirill A. Shutemov
2015-04-28 22:15 ` Kirill A. Shutemov
2015-04-28 22:38 ` Dave Hansen [this message]
2015-04-28 22:38 ` Dave Hansen
2015-04-28 22:41 ` Rik van Riel
2015-04-28 22:41 ` Rik van Riel
2015-04-28 22:54 ` Andy Lutomirski
2015-04-28 22:54 ` Andy Lutomirski
2015-04-28 22:56 ` Rik van Riel
2015-04-28 22:56 ` Rik van Riel
2015-04-28 23:01 ` Andy Lutomirski
2015-04-28 23:01 ` Andy Lutomirski
2015-04-28 23:19 ` Linus Torvalds
2015-04-28 23:19 ` Linus Torvalds
2015-04-28 23:16 ` Linus Torvalds
2015-04-28 23:16 ` Linus Torvalds
2015-04-28 23:23 ` Andy Lutomirski
2015-04-28 23:23 ` Andy Lutomirski
2015-04-28 23:38 ` Linus Torvalds
2015-04-28 23:38 ` Linus Torvalds
2015-04-28 23:49 ` Andy Lutomirski
2015-04-28 23:49 ` Andy Lutomirski
2015-04-28 22:56 ` Linus Torvalds
2015-04-28 22:56 ` Linus Torvalds
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=55400BC8.6080204@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
--cc=mgorman@suse.de \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@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.