From: Tejun Heo <tj@kernel.org>
To: "Christian Brauner" <brauner@kernel.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"John Stultz" <john.stultz@linaro.org>,
"Dmitry Shmidt" <dimitrysh@google.com>,
"Oleg Nesterov" <oleg@redhat.com>,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org
Subject: Re: [PATCH 3/3 cgroup/for-5.20] cgroup: Make !percpu threadgroup_rwsem operations optional
Date: Fri, 22 Jul 2022 19:12:07 -1000 [thread overview]
Message-ID: <YtuDJ7DijEEy3PfS@slm.duckdns.org> (raw)
In-Reply-To: <YtDvl7Qjc5zI3e/b@slm.duckdns.org>
Applying 1-3 to cgroup/for-5.20.
Thanks.
--
tejun
next prev parent reply other threads:[~2022-07-23 5:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 4:38 [PATCH 1/3 cgroup/for-5.20] cgroup: Elide write-locking threadgroup_rwsem when updating csses on an empty subtree Tejun Heo
2022-07-15 4:38 ` [PATCH 2/3 cgroup/for-5.20] cgroup: Add "no" prefixed mount options Tejun Heo
2022-07-15 4:39 ` [PATCH 3/3 cgroup/for-5.20] cgroup: Make !percpu threadgroup_rwsem operations optional Tejun Heo
2022-07-23 5:12 ` Tejun Heo [this message]
2022-07-23 14:28 ` [PATCH RESEND " Tejun Heo
2022-07-25 12:12 ` Oleg Nesterov
2022-07-26 23:14 ` Tejun Heo
2022-07-27 17:39 ` Oleg Nesterov
2022-07-25 14:16 ` Christian Brauner
2022-07-26 14:32 ` Michal Koutný
2022-07-26 17:33 ` Tejun Heo
2022-07-26 14:32 ` [PATCH 2/3 cgroup/for-5.20] cgroup: Add "no" prefixed mount options Michal Koutný
2022-07-26 20:01 ` Tejun Heo
2022-07-26 23:30 ` Tejun Heo
2022-07-26 23:48 ` [PATCH cgroup/for-5.20] cgroup: remove "no" prefixed mount options options Tejun Heo
2022-07-27 9:27 ` Michal Koutný
2022-07-27 17:55 ` Tejun Heo
2022-07-26 14:31 ` [PATCH 1/3 cgroup/for-5.20] cgroup: Elide write-locking threadgroup_rwsem when updating csses on an empty subtree Michal Koutný
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=YtuDJ7DijEEy3PfS@slm.duckdns.org \
--to=tj@kernel.org \
--cc=brauner@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=dimitrysh@google.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkoutny@suse.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.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