mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nadav Amit <namit@vmware.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Ingo Molnar <mingo@kernel.org>, Andy Lutomirski <luto@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH] x86/mm/tlb: avoid reading mm_tlb_gen when possible
Date: Mon, 6 Jun 2022 16:28:44 +0000	[thread overview]
Message-ID: <8ADBA1FC-1CFF-4B4D-907A-4CF004AAD534@vmware.com> (raw)
In-Reply-To: <84dc784b-10c9-9ade-7a20-97fe0c32f2ff@intel.com>

On Jun 6, 2022, at 8:29 AM, Dave Hansen <dave.hansen@intel.com> wrote:

> ⚠ External Email
> 
> On 3/22/22 15:07, Nadav Amit wrote:
>> +     if (f->new_tlb_gen <= local_tlb_gen) {
>> +             /*
>> +              * We are already up to date in respect to f->new_tlb_gen.
>> +              * While the core might be still behind mm_tlb_gen, checking
>> +              * mm_tlb_gen unnecessarily would have negative caching effects
>> +              * so avoid it.
>> +              */
>> +             return;
>> +     }
>> +
> 
> Nit: There's at least one "we" in here that needs to get fixed up.  I'll
> plan to do that when I apply it, but a v2 with that fixed and Peter's
> ack added might save me five minutes.

No good deed goes unpunished.

I’ll send v2 later today.

      reply	other threads:[~2022-06-06 16:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22 22:07 Nadav Amit
2022-03-28 10:35 ` Peter Zijlstra
2022-06-06 14:29   ` Nadav Amit
2022-06-06 15:29 ` Dave Hansen
2022-06-06 16:28   ` Nadav Amit [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=8ADBA1FC-1CFF-4B4D-907A-4CF004AAD534@vmware.com \
    --to=namit@vmware.com \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome