All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Shakeel Butt <shakeelb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: Wei Wang <weiwan-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
	Eric Dumazet <edumazet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	"David S . Miller"
	<davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
	Roman Gushchin
	<roman.gushchin-fxUVXftIFDnyG1zEObXtfA@public.gmane.org>
Subject: Re: [PATCH net-next] net-memcg: pass in gfp_t mask to mem_cgroup_charge_skmem()
Date: Wed, 12 Oct 2022 20:16:50 -0700	[thread overview]
Message-ID: <20221012201650.3e55331d@kernel.org> (raw)
In-Reply-To: <20221012184050.5a7f3bde-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>

On Wed, 12 Oct 2022 18:40:50 -0700 Jakub Kicinski wrote:
> Did the fact that we used to force charge not potentially cause
> reclaim, tho?  Letting TCP accept the next packet even if it had
> to drop the current one?

I pushed this little nugget to one affected machine via KLP:

diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 03ffbb255e60..c1ca369a1b77 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -7121,6 +7121,10 @@ bool mem_cgroup_charge_skmem(struct mem_cgroup *memcg, unsigned int nr_pages,
                return true;
        }
 
+       if (gfp_mask == GFP_NOWAIT) {
+               try_charge(memcg, gfp_mask|__GFP_NOFAIL, nr_pages);
+               refill_stock(memcg, nr_pages);
+       }
        return false;
 }

The problem normally reproes reliably within 10min -- 30min and counting
and the application-level latency has not spiked.

WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Shakeel Butt <shakeelb@google.com>
Cc: Wei Wang <weiwan@google.com>, Eric Dumazet <edumazet@google.com>,
	netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
	cgroups@vger.kernel.org, linux-mm@kvack.org,
	Roman Gushchin <roman.gushchin@linux.dev>
Subject: Re: [PATCH net-next] net-memcg: pass in gfp_t mask to mem_cgroup_charge_skmem()
Date: Wed, 12 Oct 2022 20:16:50 -0700	[thread overview]
Message-ID: <20221012201650.3e55331d@kernel.org> (raw)
In-Reply-To: <20221012184050.5a7f3bde@kernel.org>

On Wed, 12 Oct 2022 18:40:50 -0700 Jakub Kicinski wrote:
> Did the fact that we used to force charge not potentially cause
> reclaim, tho?  Letting TCP accept the next packet even if it had
> to drop the current one?

I pushed this little nugget to one affected machine via KLP:

diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 03ffbb255e60..c1ca369a1b77 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -7121,6 +7121,10 @@ bool mem_cgroup_charge_skmem(struct mem_cgroup *memcg, unsigned int nr_pages,
                return true;
        }
 
+       if (gfp_mask == GFP_NOWAIT) {
+               try_charge(memcg, gfp_mask|__GFP_NOFAIL, nr_pages);
+               refill_stock(memcg, nr_pages);
+       }
        return false;
 }

The problem normally reproes reliably within 10min -- 30min and counting
and the application-level latency has not spiked.


  parent reply	other threads:[~2022-10-13  3:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17 19:40 [PATCH net-next] net-memcg: pass in gfp_t mask to mem_cgroup_charge_skmem() Wei Wang
2021-08-17 19:40 ` Wei Wang
     [not found] ` <20210817194003.2102381-1-weiwan-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2021-08-18 10:50   ` patchwork-bot+netdevbpf-DgEjT+Ai2ygdnm+yROfE0A
2021-08-18 10:50     ` patchwork-bot+netdevbpf
2022-10-12 23:33   ` Jakub Kicinski
2022-10-12 23:33     ` Jakub Kicinski
     [not found]     ` <20221012163300.795e7b86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2022-10-13  0:17       ` Shakeel Butt
2022-10-13  0:17         ` Shakeel Butt
     [not found]         ` <CALvZod5pKzcxWsLnjUwE9fUb=1S9MDLOHF950miF8x8CWtK5Bw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-10-13  0:38           ` Jakub Kicinski
2022-10-13  0:38             ` Jakub Kicinski
     [not found]             ` <20221012173825.45d6fbf2-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2022-10-13  0:54               ` Shakeel Butt
2022-10-13  0:54                 ` Shakeel Butt
     [not found]                 ` <20221013005431.wzjurocrdoozykl7-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2022-10-13  1:40                   ` Jakub Kicinski
2022-10-13  1:40                     ` Jakub Kicinski
     [not found]                     ` <20221012184050.5a7f3bde-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2022-10-13  3:16                       ` Jakub Kicinski [this message]
2022-10-13  3:16                         ` Jakub Kicinski
2022-10-13  3:34                         ` Wei Wang
2022-10-13  3:49                           ` Jakub Kicinski
     [not found]                             ` <20221012204941.3223d205-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2022-10-13  4:04                               ` Wei Wang
2022-10-13  4:04                                 ` Wei Wang
2022-10-13  4:18                                 ` Shakeel Butt
2022-10-13 21:49       ` Jakub Kicinski
2022-10-13 21:49         ` Jakub Kicinski
     [not found]         ` <20221013144950.44b52f90-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2022-10-13 22:02           ` Eric Dumazet
2022-10-13 22:02             ` Eric Dumazet

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=20221012201650.3e55331d@kernel.org \
    --to=kuba-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
    --cc=edumazet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=roman.gushchin-fxUVXftIFDnyG1zEObXtfA@public.gmane.org \
    --cc=shakeelb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=weiwan-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.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 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.