All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.com>
To: Shakeel Butt <shakeelb@google.com>
Cc: "Johannes Weiner" <hannes@cmpxchg.org>,
	"Roman Gushchin" <roman.gushchin@linux.dev>,
	"Muchun Song" <songmuchun@bytedance.com>,
	"Michal Koutný" <mkoutny@suse.com>,
	"Eric Dumazet" <edumazet@google.com>,
	"Soheil Hassas Yeganeh" <soheil@google.com>,
	"Feng Tang" <feng.tang@intel.com>,
	"Oliver Sang" <oliver.sang@intel.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	lkp@lists.01.org, cgroups@vger.kernel.org, linux-mm@kvack.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] mm: page_counter: remove unneeded atomic ops for low/min
Date: Mon, 22 Aug 2022 12:18:34 +0200	[thread overview]
Message-ID: <YwNX+vq9svMynVgW@dhcp22.suse.cz> (raw)
In-Reply-To: <YwNSlZFPMgclrSCz@dhcp22.suse.cz>

On Mon 22-08-22 11:55:33, Michal Hocko wrote:
> On Mon 22-08-22 00:17:35, Shakeel Butt wrote:
[...]
> > diff --git a/mm/page_counter.c b/mm/page_counter.c
> > index eb156ff5d603..47711aa28161 100644
> > --- a/mm/page_counter.c
> > +++ b/mm/page_counter.c
> > @@ -17,24 +17,23 @@ static void propagate_protected_usage(struct page_counter *c,
> >  				      unsigned long usage)
> >  {
> >  	unsigned long protected, old_protected;
> > -	unsigned long low, min;
> >  	long delta;
> >  
> >  	if (!c->parent)
> >  		return;
> >  
> > -	min = READ_ONCE(c->min);
> > -	if (min || atomic_long_read(&c->min_usage)) {
> > -		protected = min(usage, min);
> > +	protected = min(usage, READ_ONCE(c->min));
> > +	old_protected = atomic_long_read(&c->min_usage);
> > +	if (protected != old_protected) {
> 
> I have to cache that code back into brain. It is really subtle thing and
> it is not really obvious why this is still correct. I will think about
> that some more but the changelog could help with that a lot.

OK, so the this patch will be most useful when the min > 0 && min <
usage because then the protection doesn't really change since the last
call. In other words when the usage grows above the protection and your
workload benefits from this change because that happens a lot as only a
part of the workload is protected. Correct?

Unless I have missed anything this shouldn't break the correctness but I
still have to think about the proportional distribution of the
protection because that adds to the complexity here.
-- 
Michal Hocko
SUSE Labs

WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@suse.com>
To: lkp@lists.01.org
Subject: Re: [PATCH 1/3] mm: page_counter: remove unneeded atomic ops for low/min
Date: Mon, 22 Aug 2022 12:18:34 +0200	[thread overview]
Message-ID: <YwNX+vq9svMynVgW@dhcp22.suse.cz> (raw)
In-Reply-To: <YwNSlZFPMgclrSCz@dhcp22.suse.cz>

[-- Attachment #1: Type: text/plain, Size: 1587 bytes --]

On Mon 22-08-22 11:55:33, Michal Hocko wrote:
> On Mon 22-08-22 00:17:35, Shakeel Butt wrote:
[...]
> > diff --git a/mm/page_counter.c b/mm/page_counter.c
> > index eb156ff5d603..47711aa28161 100644
> > --- a/mm/page_counter.c
> > +++ b/mm/page_counter.c
> > @@ -17,24 +17,23 @@ static void propagate_protected_usage(struct page_counter *c,
> >  				      unsigned long usage)
> >  {
> >  	unsigned long protected, old_protected;
> > -	unsigned long low, min;
> >  	long delta;
> >  
> >  	if (!c->parent)
> >  		return;
> >  
> > -	min = READ_ONCE(c->min);
> > -	if (min || atomic_long_read(&c->min_usage)) {
> > -		protected = min(usage, min);
> > +	protected = min(usage, READ_ONCE(c->min));
> > +	old_protected = atomic_long_read(&c->min_usage);
> > +	if (protected != old_protected) {
> 
> I have to cache that code back into brain. It is really subtle thing and
> it is not really obvious why this is still correct. I will think about
> that some more but the changelog could help with that a lot.

OK, so the this patch will be most useful when the min > 0 && min <
usage because then the protection doesn't really change since the last
call. In other words when the usage grows above the protection and your
workload benefits from this change because that happens a lot as only a
part of the workload is protected. Correct?

Unless I have missed anything this shouldn't break the correctness but I
still have to think about the proportional distribution of the
protection because that adds to the complexity here.
-- 
Michal Hocko
SUSE Labs

WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko-IBi9RG/b67k@public.gmane.org>
To: Shakeel Butt <shakeelb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: "Johannes Weiner"
	<hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
	"Roman Gushchin"
	<roman.gushchin-fxUVXftIFDnyG1zEObXtfA@public.gmane.org>,
	"Muchun Song"
	<songmuchun-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org>,
	"Michal Koutný" <mkoutny-IBi9RG/b67k@public.gmane.org>,
	"Eric Dumazet" <edumazet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
	"Soheil Hassas Yeganeh"
	<soheil-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
	"Feng Tang" <feng.tang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"Oliver Sang"
	<oliver.sang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"Andrew Morton"
	<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
	lkp-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org,
	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/3] mm: page_counter: remove unneeded atomic ops for low/min
Date: Mon, 22 Aug 2022 12:18:34 +0200	[thread overview]
Message-ID: <YwNX+vq9svMynVgW@dhcp22.suse.cz> (raw)
In-Reply-To: <YwNSlZFPMgclrSCz-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>

On Mon 22-08-22 11:55:33, Michal Hocko wrote:
> On Mon 22-08-22 00:17:35, Shakeel Butt wrote:
[...]
> > diff --git a/mm/page_counter.c b/mm/page_counter.c
> > index eb156ff5d603..47711aa28161 100644
> > --- a/mm/page_counter.c
> > +++ b/mm/page_counter.c
> > @@ -17,24 +17,23 @@ static void propagate_protected_usage(struct page_counter *c,
> >  				      unsigned long usage)
> >  {
> >  	unsigned long protected, old_protected;
> > -	unsigned long low, min;
> >  	long delta;
> >  
> >  	if (!c->parent)
> >  		return;
> >  
> > -	min = READ_ONCE(c->min);
> > -	if (min || atomic_long_read(&c->min_usage)) {
> > -		protected = min(usage, min);
> > +	protected = min(usage, READ_ONCE(c->min));
> > +	old_protected = atomic_long_read(&c->min_usage);
> > +	if (protected != old_protected) {
> 
> I have to cache that code back into brain. It is really subtle thing and
> it is not really obvious why this is still correct. I will think about
> that some more but the changelog could help with that a lot.

OK, so the this patch will be most useful when the min > 0 && min <
usage because then the protection doesn't really change since the last
call. In other words when the usage grows above the protection and your
workload benefits from this change because that happens a lot as only a
part of the workload is protected. Correct?

Unless I have missed anything this shouldn't break the correctness but I
still have to think about the proportional distribution of the
protection because that adds to the complexity here.
-- 
Michal Hocko
SUSE Labs

  reply	other threads:[~2022-08-22 10:18 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22  0:17 [PATCH 0/3] memcg: optimizatize charge codepath Shakeel Butt
2022-08-22  0:17 ` Shakeel Butt
2022-08-22  0:17 ` Shakeel Butt
2022-08-22  0:17 ` [PATCH 1/3] mm: page_counter: remove unneeded atomic ops for low/min Shakeel Butt
2022-08-22  0:17   ` Shakeel Butt
2022-08-22  0:17   ` Shakeel Butt
2022-08-22  0:20   ` Soheil Hassas Yeganeh
2022-08-22  0:20     ` Soheil Hassas Yeganeh
2022-08-22  0:20     ` Soheil Hassas Yeganeh
2022-08-22  2:39   ` Feng Tang
2022-08-22  2:39     ` Feng Tang
2022-08-22  2:39     ` Feng Tang
2022-08-22  9:55   ` Michal Hocko
2022-08-22  9:55     ` Michal Hocko
2022-08-22 10:18     ` Michal Hocko [this message]
2022-08-22 10:18       ` Michal Hocko
2022-08-22 10:18       ` Michal Hocko
2022-08-22 14:55       ` Shakeel Butt
2022-08-22 14:55         ` Shakeel Butt
2022-08-22 15:20         ` Michal Hocko
2022-08-22 15:20           ` Michal Hocko
2022-08-22 16:06           ` Shakeel Butt
2022-08-22 16:06             ` Shakeel Butt
2022-08-22 16:06             ` Shakeel Butt
2022-08-23  9:42           ` Michal Hocko
2022-08-23  9:42             ` Michal Hocko
2022-08-23  9:42             ` Michal Hocko
2022-08-22 18:23   ` Roman Gushchin
2022-08-22 18:23     ` Roman Gushchin
2022-08-22 18:23     ` Roman Gushchin
2022-08-22  0:17 ` [PATCH 2/3] mm: page_counter: rearrange struct page_counter fields Shakeel Butt
2022-08-22  0:17   ` Shakeel Butt
2022-08-22  0:24   ` Soheil Hassas Yeganeh
2022-08-22  0:24     ` Soheil Hassas Yeganeh
2022-08-22  0:24     ` Soheil Hassas Yeganeh
2022-08-22  4:55     ` Shakeel Butt
2022-08-22  4:55       ` Shakeel Butt
2022-08-22 13:06       ` Soheil Hassas Yeganeh
2022-08-22 13:06         ` Soheil Hassas Yeganeh
2022-08-22  2:10   ` Feng Tang
2022-08-22  2:10     ` Feng Tang
2022-08-22  2:10     ` Feng Tang
2022-08-22  4:59     ` Shakeel Butt
2022-08-22  4:59       ` Shakeel Butt
2022-08-22  4:59       ` Shakeel Butt
2022-08-22 10:23   ` Michal Hocko
2022-08-22 10:23     ` Michal Hocko
2022-08-22 10:23     ` Michal Hocko
2022-08-22 15:06     ` Shakeel Butt
2022-08-22 15:06       ` Shakeel Butt
2022-08-22 15:15       ` Michal Hocko
2022-08-22 15:15         ` Michal Hocko
2022-08-22 15:15         ` Michal Hocko
2022-08-22 16:04         ` Shakeel Butt
2022-08-22 16:04           ` Shakeel Butt
2022-08-22 18:27           ` Roman Gushchin
2022-08-22 18:27             ` Roman Gushchin
2022-08-22 18:27             ` Roman Gushchin
2022-08-22  0:17 ` [PATCH 3/3] memcg: increase MEMCG_CHARGE_BATCH to 64 Shakeel Butt
2022-08-22  0:17   ` Shakeel Butt
2022-08-22  0:24   ` Soheil Hassas Yeganeh
2022-08-22  0:24     ` Soheil Hassas Yeganeh
2022-08-22  0:24     ` Soheil Hassas Yeganeh
2022-08-22  2:30   ` Feng Tang
2022-08-22  2:30     ` Feng Tang
2022-08-22 10:47   ` Michal Hocko
2022-08-22 10:47     ` Michal Hocko
2022-08-22 10:47     ` Michal Hocko
2022-08-22 15:09     ` Shakeel Butt
2022-08-22 15:09       ` Shakeel Butt
2022-08-22 15:22       ` Michal Hocko
2022-08-22 15:22         ` Michal Hocko
2022-08-22 16:07         ` Shakeel Butt
2022-08-22 16:07           ` Shakeel Butt
2022-08-22 16:07           ` Shakeel Butt
2022-08-22 18:37   ` Roman Gushchin
2022-08-22 18:37     ` Roman Gushchin
2022-08-22 18:37     ` Roman Gushchin
2022-08-22 19:34     ` Michal Hocko
2022-08-22 19:34       ` Michal Hocko
2022-08-22 19:34       ` Michal Hocko
2022-08-23  2:22       ` Roman Gushchin
2022-08-23  2:22         ` Roman Gushchin
2022-08-23  2:22         ` Roman Gushchin
2022-08-23  4:49         ` Michal Hocko
2022-08-23  4:49           ` Michal Hocko

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=YwNX+vq9svMynVgW@dhcp22.suse.cz \
    --to=mhocko@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=feng.tang@intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@lists.01.org \
    --cc=mkoutny@suse.com \
    --cc=netdev@vger.kernel.org \
    --cc=oliver.sang@intel.com \
    --cc=roman.gushchin@linux.dev \
    --cc=shakeelb@google.com \
    --cc=soheil@google.com \
    --cc=songmuchun@bytedance.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 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.