From: Rik van Riel <riel@surriel.com>
To: Andy Lutomirski <luto@kernel.org>
Cc: songliubraving@fb.com, Mike Galbraith <efault@gmx.de>,
LKML <linux-kernel@vger.kernel.org>,
kernel-team <Kernel-team@fb.com>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>, X86 ML <x86@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] x86,switch_mm: skip atomic operations for init_mm
Date: Wed, 06 Jun 2018 15:00:03 -0400 [thread overview]
Message-ID: <1528311603.7898.136.camel@surriel.com> (raw)
In-Reply-To: <CALCETrU6bqVyBzeMu9RSoXq1Fm6rdHA6rDskqVqo5+W9snkz=A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]
On Wed, 2018-06-06 at 11:17 -0700, Andy Lutomirski wrote:
> On Sat, Jun 2, 2018 at 6:38 PM Rik van Riel <riel@surriel.com> wrote:
> >
> > On Sun, 2018-06-03 at 00:51 +0000, Song Liu wrote:
> >
> > > > Just to check: in the workload where you're seeing this
> > > > problem,
> > > > are
> > > > you using an mm with many threads? I would imagine that, if
> > > > you
> > > > only
> > > > have one or two threads, the bit operations aren't so bad.
> > >
> > > Yes, we are running netperf/netserver with 300 threads. We don't
> > > see
> > > this much overhead in with real workload.
> >
> > We may not, but there are some crazy workloads out
> > there in the world. Think of some Java programs with
> > thousands of threads, causing a million context
> > switches a second on a large system.
> >
> > I like Andy's idea of having one cache line with
> > a cpumask per node. That seems like it will have
> > fewer downsides for tasks with fewer threads running
> > on giant systems.
> >
> > I'll throw out the code I was working on, and look
> > into implementing that :)
> >
>
> I'm not sure you should throw your patch out. It's a decent idea,
> too.
Oh, I still have it saved, but the cpumask per
NUMA node looks like it could have a big impact,
with less guesswork or side effects.
--
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-06-06 19:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 12:28 [PATCH] x86,switch_mm: skip atomic operations for init_mm Rik van Riel
2018-06-01 15:11 ` Andy Lutomirski
2018-06-01 18:22 ` Rik van Riel
2018-06-01 18:48 ` Mike Galbraith
2018-06-01 19:43 ` Rik van Riel
2018-06-01 20:03 ` Andy Lutomirski
2018-06-01 20:35 ` Rik van Riel
2018-06-01 21:21 ` Andy Lutomirski
2018-06-01 22:13 ` Rik van Riel
2018-06-02 3:35 ` Andy Lutomirski
2018-06-02 5:04 ` Rik van Riel
2018-06-02 20:14 ` Andy Lutomirski
2018-06-03 0:51 ` Song Liu
2018-06-03 1:38 ` Rik van Riel
2018-06-06 18:17 ` Andy Lutomirski
2018-06-06 19:00 ` Rik van Riel [this message]
2018-06-06 19:23 ` Andy Lutomirski
2018-06-02 3:39 ` Mike Galbraith
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=1528311603.7898.136.camel@surriel.com \
--to=riel@surriel.com \
--cc=Kernel-team@fb.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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