From: Tejun Heo <tj@kernel.org>
To: Tim Hockin <thockin@hockin.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Li Zefan <lizf@cn.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Paul Menage <paul@paulmenage.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Aditya Kali <adityakali@google.com>,
Oleg Nesterov <oleg@redhat.com>,
Containers <containers@lists.linux-foundation.org>,
Glauber Costa <glommer@gmail.com>,
Cgroups <cgroups@vger.kernel.org>,
Daniel J Walsh <dwalsh@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Max Kellermann <mk@cm4all.com>,
Mandeep Singh Baines <msb@chromium.org>
Subject: Re: [PATCH 00/10] cgroups: Task counter subsystem v8
Date: Mon, 1 Apr 2013 16:18:24 -0700 [thread overview]
Message-ID: <20130401231824.GC2487@htj.dyndns.org> (raw)
In-Reply-To: <CAAAKZwvdMUAZ+N5d-cdCJbKUq=t9M6BbCxzOTWnVQQBrg55vhw@mail.gmail.com>
Hello,
On Mon, Apr 01, 2013 at 03:57:46PM -0700, Tim Hockin wrote:
> I am not limited by kernel memory, I am limited by PIDs, and I need to
> be able to manage them. memory.kmem.usage_in_bytes seems to be far
> too noisy to be useful for this purpose. It may work fine for "just
> stop a fork bomb" but not for any sort of finer-grained control.
So, why are you limited by PIDs other than the arcane / weird
limitation that you have whereever that limitation is?
> > If you think you can tilt it the other way, please feel free to try.
>
> Just because others caved, doesn't make it less of a hack. And I will
> cave, too, because I don't have time to bang my head against a wall,
> especially when I can see the remnants of other people who have tried.
>
> We'll work around it, or we'll hack around it, or we'll carry this
> patch in our own tree and just grumble about ridiculous hacks every
> time we have to forward port it.
>
> I was just hoping that things had worked themselves out in the last year.
It's kinda weird getting this response, as I don't think it has been
particularly walley. The arguments were pretty sound from what I
recall and Frederic's use case was actually better covered by kmemcg,
so where's the said wall? And I asked you why your use case is
different and the only reason you gave me is some arbitrary PID
limitation on whatever thing you're using, which you gotta agree is a
pretty hard sell. So, if you think you have a valid case, please just
explain it. Why go passive agressive on it? If you don't have a
valid case for pushing it, yes, you'll have to hack around it - carry
the patches in your tree, whatever, or better, fix the weird PID
problem.
--
tejun
next prev parent reply other threads:[~2013-04-01 23:18 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 3:37 [PATCH 00/10] cgroups: Task counter subsystem v8 Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 01/10] cgroups: add res_counter_write_u64() API Frederic Weisbecker
2012-02-02 12:33 ` Kirill A. Shutemov
2012-02-02 13:56 ` Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 02/10] cgroups: new resource counter inheritance API Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 03/10] cgroups: ability to stop res charge propagation on bounded ancestor Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 04/10] cgroups: add res counter common ancestor searching Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 05/10] res_counter: allow charge failure pointer to be null Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 06/10] cgroups: pull up res counter charge failure interpretation to caller Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 07/10] cgroups: allow subsystems to cancel a fork Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 08/10] cgroups: Add a task counter subsystem Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 09/10] selftests: Enter each directories before executing selftests Frederic Weisbecker
2012-02-01 3:37 ` [PATCH 10/10] selftests: Add a new task counter selftest Frederic Weisbecker
2012-02-01 16:31 ` [PATCH 00/10] cgroups: Task counter subsystem v8 Tejun Heo
2012-02-01 18:50 ` Frederic Weisbecker
2012-02-01 19:51 ` Andrew Morton
2012-02-02 14:50 ` Frederic Weisbecker
2012-02-16 15:31 ` Frederic Weisbecker
2012-03-01 22:53 ` Daniel Lezcano
2012-03-05 3:21 ` Frederic Weisbecker
2012-03-05 16:26 ` Tejun Heo
2012-03-05 16:27 ` Tejun Heo
2012-03-05 16:48 ` Frederic Weisbecker
2012-03-05 16:44 ` Rik van Riel
2013-04-01 18:43 ` Tim Hockin
2013-04-01 18:46 ` Tejun Heo
2013-04-01 20:09 ` Tim Hockin
2013-04-01 20:29 ` Tejun Heo
2013-04-01 21:02 ` Tim Hockin
2013-04-01 22:03 ` Tejun Heo
2013-04-01 22:20 ` Tim Hockin
2013-04-01 22:35 ` Tejun Heo
2013-04-01 22:57 ` Tim Hockin
2013-04-01 23:18 ` Tejun Heo [this message]
2013-04-02 0:07 ` Tim Hockin
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=20130401231824.GC2487@htj.dyndns.org \
--to=tj@kernel.org \
--cc=adityakali@google.com \
--cc=akpm@linux-foundation.org \
--cc=berrange@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=dwalsh@redhat.com \
--cc=fweisbec@gmail.com \
--cc=glommer@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mk@cm4all.com \
--cc=msb@chromium.org \
--cc=oleg@redhat.com \
--cc=paul@paulmenage.org \
--cc=thockin@hockin.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).