From: brookxu <brookxu.cn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Tejun Heo" <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"Michal Koutný" <mkoutny-IBi9RG/b67k@public.gmane.org>
Cc: lizefan.x-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org,
hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org,
vipinsh-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2] misc_cgroup: use a counter to count the number of failures
Date: Wed, 25 Aug 2021 14:50:38 +0800 [thread overview]
Message-ID: <75e53c51-396d-cce2-65ed-70fb60e226bd@gmail.com> (raw)
In-Reply-To: <YSVDwc/1sEmXdOK9-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org>
Tejun Heo wrote on 2021/8/25 3:08:
> Hello,
>
> On Tue, Aug 24, 2021 at 06:44:23PM +0200, Michal Koutný wrote:
>> However, the non-hierarchical failcnt interface looks like v1ism to me
>> (I think new features should come with v2 first in mind).
>> What about exposing this in misc.events file with max.$res_name entries?
>
> Ah yeah, good point. misc.events sounds like a good spot to put these.
>
>> Or if the hierarchical reporting is unnecessary now, there can be just
>> misc.events.local for starters.
>
> I'd prefer to stick with hierarchical counting as the first step at least.
>
>> (That reminds me the forgotten pids.events[.local] rework [1], oops.)
>>
>> https://lore.kernel.org/lkml/20191128172612.10259-1-mkoutny-IBi9RG/b67k@public.gmane.org/#t
>
> I think both counters are useful - the number of failures due to this type
> of limit in this subhierarchy, and the number of failures caused by this
> particular limit in this subhierarchy. It's a pretty subtle difference to
> encapsulate in a counter name tho.
Thanks all for good suggestion, I try to do it in next version.
> Thanks.
>
WARNING: multiple messages have this Message-ID (diff)
From: brookxu <brookxu.cn@gmail.com>
To: "Tejun Heo" <tj@kernel.org>, "Michal Koutný" <mkoutny@suse.com>
Cc: lizefan.x@bytedance.com, hannes@cmpxchg.org, vipinsh@google.com,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org
Subject: Re: [PATCH v2] misc_cgroup: use a counter to count the number of failures
Date: Wed, 25 Aug 2021 14:50:38 +0800 [thread overview]
Message-ID: <75e53c51-396d-cce2-65ed-70fb60e226bd@gmail.com> (raw)
In-Reply-To: <YSVDwc/1sEmXdOK9@slm.duckdns.org>
Tejun Heo wrote on 2021/8/25 3:08:
> Hello,
>
> On Tue, Aug 24, 2021 at 06:44:23PM +0200, Michal Koutný wrote:
>> However, the non-hierarchical failcnt interface looks like v1ism to me
>> (I think new features should come with v2 first in mind).
>> What about exposing this in misc.events file with max.$res_name entries?
>
> Ah yeah, good point. misc.events sounds like a good spot to put these.
>
>> Or if the hierarchical reporting is unnecessary now, there can be just
>> misc.events.local for starters.
>
> I'd prefer to stick with hierarchical counting as the first step at least.
>
>> (That reminds me the forgotten pids.events[.local] rework [1], oops.)
>>
>> https://lore.kernel.org/lkml/20191128172612.10259-1-mkoutny@suse.com/#t
>
> I think both counters are useful - the number of failures due to this type
> of limit in this subhierarchy, and the number of failures caused by this
> particular limit in this subhierarchy. It's a pretty subtle difference to
> encapsulate in a counter name tho.
Thanks all for good suggestion, I try to do it in next version.
> Thanks.
>
next prev parent reply other threads:[~2021-08-25 6:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 0:15 [PATCH v2] misc_cgroup: use a counter to count the number of failures brookxu
2021-08-14 0:15 ` brookxu
[not found] ` <a09f381462b1ce9c506a22713b998e21b459f7e9.1628899295.git.brookxu-1Nz4purKYjRBDgjK7y7TUQ@public.gmane.org>
2021-08-14 1:16 ` Vipin Sharma
2021-08-14 1:16 ` Vipin Sharma
2021-08-24 16:44 ` Michal Koutný
2021-08-24 16:44 ` Michal Koutný
[not found] ` <20210824164423.GA11859-9OudH3eul5jcvrawFnH+a6VXKuFTiq87@public.gmane.org>
2021-08-24 19:08 ` Tejun Heo
2021-08-24 19:08 ` Tejun Heo
[not found] ` <YSVDwc/1sEmXdOK9-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org>
2021-08-25 6:50 ` brookxu [this message]
2021-08-25 6:50 ` brookxu
2021-08-26 1:34 ` brookxu
2021-08-26 1:34 ` brookxu
[not found] ` <4ed67493-e595-e002-69f9-1f53662ba189-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-08-26 11:29 ` Michal Koutný
2021-08-26 11:29 ` Michal Koutný
[not found] ` <20210826112954.GD4520-9OudH3eul5jcvrawFnH+a6VXKuFTiq87@public.gmane.org>
2021-09-08 5:29 ` brookxu
2021-09-08 5:29 ` brookxu
[not found] ` <49057879-92a9-958a-ac30-057ceabd1b7f-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-09-09 15:01 ` Michal Koutný
2021-09-09 15:01 ` 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=75e53c51-396d-cce2-65ed-70fb60e226bd@gmail.com \
--to=brookxu.cn-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan.x-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org \
--cc=mkoutny-IBi9RG/b67k@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=vipinsh-hpIqsD4AKlfQT0dZR+AlfA@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 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.