All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Will Deacon <will@kernel.org>, Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, bigeasy@linutronix.de,
	juri.lelli@redhat.com, williams@redhat.com, bristot@redhat.com,
	longman@redhat.com, dave@stgolabs.net, jack@suse.com
Subject: Re: [PATCH] locking/percpu_rwsem: Rewrite to not use rwsem
Date: Wed, 30 Oct 2019 16:57:20 +0100	[thread overview]
Message-ID: <20191030155720.GA20713@redhat.com> (raw)
In-Reply-To: <20191029190624.GB3079@worktop.programming.kicks-ass.net>

On 10/29, Peter Zijlstra wrote:
>
> That said, I think cgroups use a variant of percpu-rwsem that wreck rss
> on purpose and always take the slowpaths.

I forgot (never understodd) why does Android need this.

I am wondering if it makes any sense to add a config/boot or even runtime
knob for cgroup_threadgroup_rwsem.

Oleg.


  reply	other threads:[~2019-10-30 15:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-05 14:02 [PATCH] locking/percpu_rwsem: Rewrite to not use rwsem Peter Zijlstra
2019-08-05 14:43 ` Boqun Feng
2019-08-05 14:58   ` Boqun Feng
2019-08-05 15:43     ` Peter Zijlstra
2019-08-06 14:15       ` Boqun Feng
2019-08-06 16:17 ` Oleg Nesterov
2019-08-06 17:15   ` Peter Zijlstra
2019-08-07  9:56     ` Oleg Nesterov
2019-10-29 18:47       ` Peter Zijlstra
2019-10-30 14:21         ` Oleg Nesterov
2019-10-30 16:09           ` Peter Zijlstra
2019-10-30 17:52         ` Peter Zijlstra
2019-10-30 18:47           ` Peter Zijlstra
2019-10-30 19:31           ` Peter Zijlstra
2019-10-31  6:11           ` Peter Zijlstra
2019-08-07 14:45 ` Will Deacon
2019-10-29 19:06   ` Peter Zijlstra
2019-10-30 15:57     ` Oleg Nesterov [this message]
2019-10-30 16:47       ` Peter Zijlstra

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=20191030155720.GA20713@redhat.com \
    --to=oleg@redhat.com \
    --cc=bigeasy@linutronix.de \
    --cc=bristot@redhat.com \
    --cc=dave@stgolabs.net \
    --cc=jack@suse.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=will@kernel.org \
    --cc=williams@redhat.com \
    /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.