From: Rik van Riel <riel@surriel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, luto@kernel.org,
dave.hansen@intel.com, kernel-team@fb.com, efault@gmx.de,
tglx@linutronix.de, songliubraving@fb.com, hpa@zytor.com
Subject: Re: [PATCH 7/7] x86,switch_mm: skip atomic operations for init_mm
Date: Mon, 16 Jul 2018 14:37:04 -0400 [thread overview]
Message-ID: <1531766224.26425.5.camel@surriel.com> (raw)
In-Reply-To: <20180716010457.GA28744@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]
On Mon, 2018-07-16 at 03:04 +0200, Ingo Molnar wrote:
> * Rik van Riel <riel@surriel.com> wrote:
>
> > On Mon, 2018-07-16 at 01:04 +0200, Ingo Molnar wrote:
> > > * Rik van Riel <riel@surriel.com> wrote:
> > >
> > > > + /*
> > > > + * Stop remote flushes for the previous mm.
> > > > + * Skip the idle task; we never send init_mm
> > > > TLB
> > > > flushing IPIs,
> > > > + * but the bitmap manipulation can cause cache
> > > > line contention.
> > > > + */
> > > > + if (real_prev != &init_mm) {
> > > > + VM_WARN_ON_ONCE(!cpumask_test_cpu(cpu,
> > > > + mm_cpumask(rea
> > > > l_pr
> > > > ev)));
> > > > + cpumask_clear_cpu(cpu,
> > > > mm_cpumask(real_prev));
> > >
> > > BTW., could this optimization be (safely) extended to all (or
> > > most)
> > > !task->mm
> > > kernel threads?
> > >
> > > In particular softirq and threaded irq handlers could benefit
> > > greatly
> > > I suspect in
> > > certain networking intense workloads that happen to active them.
> >
> > Yes, it could.
> >
> > Are there kernel threads that use something other than
> > init_mm today?
>
> Yeah, I think that's the typical case - so at minimum the comment
> should be fixed:
>
> > > > + * Skip the idle task; we never send init_mm TLB
> flushing IPIs,
>
> and it should say 'skip kernel threads', right?
I will send a v6 that improves this comment, and has
the S-o-b thing you suggested for patch 1/7.
I think that addresses all the comments people had on
this patch series.
--
All Rights Reversed.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-07-16 18:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 14:28 [PATCH v5 0/7] x86,tlb,mm: make lazy TLB mode even lazier Rik van Riel
2018-07-10 14:28 ` [PATCH 1/7] mm: allocate mm_cpumask dynamically based on nr_cpu_ids Rik van Riel
2018-07-15 22:59 ` Ingo Molnar
2018-07-15 23:50 ` Rik van Riel
2018-07-16 1:07 ` Ingo Molnar
2018-07-10 14:28 ` [PATCH 2/7] x86,tlb: leave lazy TLB mode at page table free time Rik van Riel
2018-07-10 14:28 ` [PATCH 3/7] x86,mm: restructure switch_mm_irqs_off Rik van Riel
2018-07-10 14:28 ` [PATCH 4/7] x86,tlb: make lazy TLB mode lazier Rik van Riel
2018-07-10 14:28 ` [PATCH 5/7] x86,tlb: only send page table free TLB flush to lazy TLB CPUs Rik van Riel
2018-07-10 14:28 ` [PATCH 6/7] x86,mm: always use lazy TLB mode Rik van Riel
2018-07-10 14:28 ` [PATCH 7/7] x86,switch_mm: skip atomic operations for init_mm Rik van Riel
2018-07-15 23:04 ` Ingo Molnar
2018-07-15 23:49 ` Rik van Riel
2018-07-16 1:04 ` Ingo Molnar
2018-07-16 18:37 ` Rik van Riel [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-16 19:03 [PATCH v6 0/7] x86,tlb,mm: make lazy TLB mode even lazier Rik van Riel
2018-07-16 19:03 ` [PATCH 7/7] x86,switch_mm: skip atomic operations for init_mm Rik van Riel
2018-07-06 21:56 [PATCH v4 0/7] x86,tlb,mm: make lazy TLB mode even lazier Rik van Riel
2018-07-06 21:56 ` [PATCH 7/7] x86,switch_mm: skip atomic operations for init_mm Rik van Riel
2018-06-29 14:29 [PATCH v3 0/7] x86,tlb,mm: make lazy TLB mode even lazier Rik van Riel
2018-06-29 14:29 ` [PATCH 7/7] x86,switch_mm: skip atomic operations for init_mm Rik van Riel
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=1531766224.26425.5.camel@surriel.com \
--to=riel@surriel.com \
--cc=dave.hansen@intel.com \
--cc=efault@gmx.de \
--cc=hpa@zytor.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=songliubraving@fb.com \
--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