From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f200.google.com (mail-wr0-f200.google.com [209.85.128.200]) by kanga.kvack.org (Postfix) with ESMTP id A703C6B02C3 for ; Tue, 18 Jul 2017 04:53:46 -0400 (EDT) Received: by mail-wr0-f200.google.com with SMTP id w63so2905519wrc.5 for ; Tue, 18 Jul 2017 01:53:46 -0700 (PDT) Received: from mail-wr0-x242.google.com (mail-wr0-x242.google.com. [2a00:1450:400c:c0c::242]) by mx.google.com with ESMTPS id 62si12478268wmv.29.2017.07.18.01.53.45 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Jul 2017 01:53:45 -0700 (PDT) Received: by mail-wr0-x242.google.com with SMTP id a10so3131795wrd.2 for ; Tue, 18 Jul 2017 01:53:45 -0700 (PDT) Date: Tue, 18 Jul 2017 10:53:42 +0200 From: Ingo Molnar Subject: Re: [PATCH v4 10/10] x86/mm: Try to preserve old TLB entries using PCID Message-ID: <20170718085341.nlt35dph4oukb4tc@gmail.com> References: <20170705121807.GF4941@worktop> <20170705170219.ogjnswef3ufgeklz@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170705170219.ogjnswef3ufgeklz@hirez.programming.kicks-ass.net> Sender: owner-linux-mm@kvack.org List-ID: To: Peter Zijlstra Cc: Andy Lutomirski , X86 ML , "linux-kernel@vger.kernel.org" , Borislav Petkov , Linus Torvalds , Andrew Morton , Mel Gorman , "linux-mm@kvack.org" , Nadav Amit , Rik van Riel , Dave Hansen , Arjan van de Ven * Peter Zijlstra wrote: > On Wed, Jul 05, 2017 at 09:04:39AM -0700, Andy Lutomirski wrote: > > On Wed, Jul 5, 2017 at 5:18 AM, Peter Zijlstra wrote: > > > On Thu, Jun 29, 2017 at 08:53:22AM -0700, Andy Lutomirski wrote: > > >> @@ -104,18 +140,20 @@ void switch_mm_irqs_off(struct mm_struct *prev, struct mm_struct *next, > > >> > > >> /* Resume remote flushes and then read tlb_gen. */ > > >> cpumask_set_cpu(cpu, mm_cpumask(next)); > > > > > > Barriers should have a comment... what is being ordered here against > > > what? > > > > How's this comment? > > > > /* > > * Resume remote flushes and then read tlb_gen. We need to do > > * it in this order: any inc_mm_tlb_gen() caller that writes a > > * larger tlb_gen than we read here must see our cpu set in > > * mm_cpumask() so that it will know to flush us. The barrier > > * here synchronizes with inc_mm_tlb_gen(). > > */ > > Slightly confusing, you mean this, right? > > > cpumask_set_cpu(cpu, mm_cpumask()); inc_mm_tlb_gen(); > > MB MB > > next_tlb_gen = atomic64_read(&next->context.tlb_gen); flush_tlb_others(mm_cpumask()); > > > which seems to make sense. Btw., I'll wait for a v5 iteration before applying this last patch to tip:x86/mm. Thanks, Ingo -- 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: email@kvack.org