linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ivan Teterevkov <ivan.teterevkov@nutanix.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: "rientjes@google.com" <rientjes@google.com>,
	"willy@infradead.org" <willy@infradead.org>,
	"vbabka@suse.cz" <vbabka@suse.cz>,
	"tj@kernel.org" <tj@kernel.org>,
	"lizefan@huawei.com" <lizefan@huawei.com>,
	"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
	"corbet@lwn.net" <corbet@lwn.net>,
	"vdavydov.dev@gmail.com" <vdavydov.dev@gmail.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"guro@fb.com" <guro@fb.com>,
	"shakeelb@google.com" <shakeelb@google.com>,
	"chris@chrisdown.name" <chris@chrisdown.name>,
	"yang.shi@linux.alibaba.com" <yang.shi@linux.alibaba.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"minchan@kernel.org" <minchan@kernel.org>,
	"ying.huang@intel.com" <ying.huang@intel.com>,
	"ziqian.lzq@antfin.com" <ziqian.lzq@antfin.com>,
	"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Jonathan Davies <jond@nutanix.com>
Subject: RE: [RFC] memcg: fix default behaviour of non-overridden memcg.swappiness
Date: Tue, 14 Apr 2020 16:08:39 +0000	[thread overview]
Message-ID: <MN2PR02MB63033A5D2EE11A0D7DFEBE95E9DA0@MN2PR02MB6303.namprd02.prod.outlook.com> (raw)
In-Reply-To: <20200320134428.GG24409@dhcp22.suse.cz>

On Fri, 20 Mar 2020, Michal Hocko wrote:
> On Thu 19-03-20 17:38:30, Ivan Teterevkov wrote:
> > Also, shall this magic -1 be exposed to the user? I think it's a "no",
> > but what if the user wants to un-override the memcg.swappiness...
> 
> If we are to use such a semantic then it absolutely has to be an opt-in behavior
> and expressed in some way to the user space (e.g. a symbolic name referring to
> the global setting).

A symbolic link would be a good approach but...

> I am not convinced we need it.

... agree and not going any further with the suggestion.

Support of the sysctl parameters in the kernel command line is a
better solution and would address my initially raised concern to
tackle the configuration parameters.

Thanks
Ivan


      reply	other threads:[~2020-04-14 18:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19 17:38 Ivan Teterevkov
2020-03-20 13:44 ` Michal Hocko
2020-04-14 16:08   ` Ivan Teterevkov [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=MN2PR02MB63033A5D2EE11A0D7DFEBE95E9DA0@MN2PR02MB6303.namprd02.prod.outlook.com \
    --to=ivan.teterevkov@nutanix.com \
    --cc=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=chris@chrisdown.name \
    --cc=corbet@lwn.net \
    --cc=guro@fb.com \
    --cc=hannes@cmpxchg.org \
    --cc=jond@nutanix.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lizefan@huawei.com \
    --cc=mhocko@kernel.org \
    --cc=minchan@kernel.org \
    --cc=rientjes@google.com \
    --cc=shakeelb@google.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=vbabka@suse.cz \
    --cc=vdavydov.dev@gmail.com \
    --cc=willy@infradead.org \
    --cc=yang.shi@linux.alibaba.com \
    --cc=ying.huang@intel.com \
    --cc=ziqian.lzq@antfin.com \
    /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