From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Aleksa Sarai <cyphar-gVpy/LI/lHzQT0dZR+AlfA@public.gmane.org>
Cc: "Li Zefan" <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
"Ingo Molnar" <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"Peter Zijlstra" <peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
"Richard Weinberger" <richard-/L3Ra7n9ekc@public.gmane.org>,
"Frédéric Weisbecker"
<fweisbec-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Cgroups <cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v13 4/5] cgroup: allow a cgroup subsystem to reject a fork
Date: Tue, 9 Jun 2015 16:23:07 +0900 [thread overview]
Message-ID: <CAOS58YM9nUYGP_f3_CE4EoaFGJ=aB3EJC43xrJwc_iymLf+rXQ@mail.gmail.com> (raw)
In-Reply-To: <CAOviyai2LMkFJuOhc=ZEckuackTnfPBwCsB6aLxTBJD3-vb1=w@mail.gmail.com>
Hello,
On Tue, Jun 9, 2015 at 4:20 PM, Aleksa Sarai <cyphar-gVpy/LI/lHzQT0dZR+AlfA@public.gmane.org> wrote:
> CGROUP_CANFORK_{START,END,COUNT} aren't used to restrict the
> iteration. They're used for restricting the size of the @ss_priv
> array. If you want, I can use CANFORK_{START,END} to restrict the
> iteration -- I just prefer using the for_each_subsys_which API for
> iterating over active cgroups. :/
Ah, I see. Hmm... yeah, let's keep the code for now, but I think it'd
be cheaper / cleaner to use those macro tags to restrict iteration and
drop all the masks in the future.
Thanks.
--
tejun
next prev parent reply other threads:[~2015-06-09 7:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 23:42 [PATCH v13 0/5] cgroup: add PIDs subsystem Aleksa Sarai
2015-06-06 0:02 ` [PATCH v13 1/5] cgroup: use bitmask to filter for_each_subsys Aleksa Sarai
[not found] ` <1433547736-11707-1-git-send-email-cyphar-gVpy/LI/lHzQT0dZR+AlfA@public.gmane.org>
2015-06-06 0:02 ` [PATCH v13 2/5] cgroup: replace explicit ss_mask checking with for_each_subsys_which Aleksa Sarai
[not found] ` <1433548938-32560-2-git-send-email-cyphar-gVpy/LI/lHzQT0dZR+AlfA@public.gmane.org>
2015-06-08 9:21 ` Tejun Heo
2015-06-06 0:02 ` [PATCH v13 3/5] cgroup, block: implement task_get_css() Aleksa Sarai
2015-06-08 9:22 ` Tejun Heo
2015-06-06 0:02 ` [PATCH v13 4/5] cgroup: allow a cgroup subsystem to reject a fork Aleksa Sarai
[not found] ` <1433548938-32560-4-git-send-email-cyphar-gVpy/LI/lHzQT0dZR+AlfA@public.gmane.org>
2015-06-09 4:41 ` Tejun Heo
[not found] ` <20150609044133.GQ21465-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2015-06-09 7:20 ` Aleksa Sarai
2015-06-09 7:23 ` Tejun Heo [this message]
2015-06-06 0:02 ` [PATCH v13 5/5] cgroup: implement the PIDs subsystem Aleksa Sarai
[not found] ` <1433548938-32560-5-git-send-email-cyphar-gVpy/LI/lHzQT0dZR+AlfA@public.gmane.org>
2015-06-09 4:56 ` Tejun Heo
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='CAOS58YM9nUYGP_f3_CE4EoaFGJ=aB3EJC43xrJwc_iymLf+rXQ@mail.gmail.com' \
--to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=cyphar-gVpy/LI/lHzQT0dZR+AlfA@public.gmane.org \
--cc=fweisbec-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=richard-/L3Ra7n9ekc@public.gmane.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;
as well as URLs for NNTP newsgroup(s).