Linux cgroups development
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: brookxu <brookxu.cn@gmail.com>
Cc: viro@zeniv.linux.org.uk, lizefan.x@bytedance.com,
	hannes@cmpxchg.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, cgroups@vger.kernel.org
Subject: Re: [RFC PATCH v2 1/3] misc_cgroup: add support for nofile limit
Date: Wed, 28 Jul 2021 05:38:39 -1000	[thread overview]
Message-ID: <YQF5/8Zb/iY5DS7f@mtj.duckdns.org> (raw)
In-Reply-To: <ed8824d5-0557-7d38-97bd-18d6795faa55@gmail.com>

Hello,

On Wed, Jul 28, 2021 at 05:47:05PM +0800, brookxu wrote:
> But considering stability issues(k8s), There are still many production environments use
> cgroup v1 without kmem. If kmem is enabled, due to the relatively large granularity
> of kmem, this feature can also prevent the abnormal open behavior from making the entire
> container unavailable? but I currently do not have this scenario.

Now we are repeating the same points. This simply doesn't justify adding a
user-facing feature that we have to maintain for eternity.

Thanks.

-- 
tejun

  reply	other threads:[~2021-07-28 15:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-22 15:20 [RFC PATCH v2 1/3] misc_cgroup: add support for nofile limit brookxu
2021-07-22 15:20 ` [RFC PATCH v2 2/3] misc_cgroup: add failcnt counter brookxu
     [not found] ` <3fd94563b4949ffbfe10e7d18ac1df3852b103a6.1626966339.git.brookxu-1Nz4purKYjRBDgjK7y7TUQ@public.gmane.org>
2021-07-22 15:20   ` [RFC PATCH v2 3/3] misc_cgroup: delete failed logs to avoid log flooding brookxu
2021-07-26 21:27 ` [RFC PATCH v2 1/3] misc_cgroup: add support for nofile limit Tejun Heo
     [not found]   ` <YP8ovYqISzKC43mt-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2021-07-27  3:18     ` brookxu
     [not found]       ` <b2ff6f80-8ec6-e260-ec42-2113e8ce0a18-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2021-07-27 16:32         ` Tejun Heo
2021-07-28  3:17           ` brookxu
2021-07-28  7:41             ` Tejun Heo
     [not found]               ` <YQEKNPrrOuyxTarN-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2021-07-28  9:47                 ` brookxu
2021-07-28 15:38                   ` Tejun Heo [this message]
     [not found]                     ` <YQF5/8Zb/iY5DS7f-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2021-07-29  6:37                       ` brookxu

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=YQF5/8Zb/iY5DS7f@mtj.duckdns.org \
    --to=tj@kernel.org \
    --cc=brookxu.cn@gmail.com \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan.x@bytedance.com \
    --cc=viro@zeniv.linux.org.uk \
    /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