linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Frank Vosberg <frank.vosberg@sscs.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Kernel problem
Date: Fri, 12 May 2017 07:56:55 +0200	[thread overview]
Message-ID: <20170512055655.GA6803@dhcp22.suse.cz> (raw)
In-Reply-To: <bbde3fc7-fa8c-7872-1099-44a3c293ffba@infradead.org>

On Thu 11-05-17 09:57:25, Randy Dunlap wrote:
[...]
> I'll let someone else comment on the actual warning message:
> Creating hierarchies with use_hierarchy==0 (flat hierarchy) is considered deprecated. If you believe that your setup is correct, we kindly ask you to contact linux-mm@kvack.org and let us know

Well, this warning just says that using not hierarchical memory cgroup
hierarchy is a bad idea and this behavior will not be supported for ever
(or for v2 cgroup for that matter). It should warn users who are using
old kernels to either change their configuration or complain that they
have a valid usecase for such a configuration so that we can think of an
alternative approach. From the original email it is not clear to me
whether this configuration is intentional or not, though.
-- 
Michal Hocko
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      parent reply	other threads:[~2017-05-12  5:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11 15:17 Kernel problem Frank Vosberg
2017-05-11 16:57 ` Randy Dunlap
2017-05-11 17:30   ` AW: " Frank Vosberg
2017-05-12  5:56   ` Michal Hocko [this message]

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=20170512055655.GA6803@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=frank.vosberg@sscs.com \
    --cc=linux-mm@kvack.org \
    --cc=rdunlap@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;
as well as URLs for NNTP newsgroup(s).