From: Shakeel Butt <shakeelb@google.com>
To: Zhang@google.com, Cathy <cathy.zhang@intel.com>
Cc: Eric Dumazet <edumazet@google.com>, Linux MM <linux-mm@kvack.org>,
Cgroups <cgroups@vger.kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
Brandeburg@google.com, Jesse <jesse.brandeburg@intel.com>,
Srinivas@google.com, Suresh <suresh.srinivas@intel.com>,
Chen@google.com, Tim C <tim.c.chen@intel.com>,
You@google.com, Lizhen <lizhen.you@intel.com>,
"eric.dumazet@gmail.com" <eric.dumazet@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 1/2] net: Keep sk->sk_forward_alloc as a proper size
Date: Thu, 11 May 2023 21:18:42 +0000 [thread overview]
Message-ID: <20230511211338.oi4xwoueqmntsuna@google.com> (raw)
In-Reply-To: <IA0PR11MB73557DEAB912737FD61D2873FC749@IA0PR11MB7355.namprd11.prod.outlook.com>
On Thu, May 11, 2023 at 09:26:46AM +0000, Zhang, Cathy wrote:
>
[...]
>
> 8.98% mc-worker [kernel.vmlinux] [k] page_counter_cancel
> |
> --8.97%--page_counter_cancel
> |
> --8.97%--page_counter_uncharge
> drain_stock
> __refill_stock
> refill_stock
> |
> --8.91%--try_charge_memcg
> mem_cgroup_charge_skmem
I do want to understand for above which specific condition in
__refill_stock is causing to drain stock in the charge code path. Can
you please re-run and profile your test with following code snippet (or
use any other mechanism which can answer the question)?
From f1d91043f21f4b29717c78615b374d79fc021d1f Mon Sep 17 00:00:00 2001
From: Shakeel Butt <shakeelb@google.com>
Date: Thu, 11 May 2023 20:00:19 +0000
Subject: [PATCH] Debug drain on charging.
---
mm/memcontrol.c | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index d31fb1e2cb33..4c1c3d90a4a3 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -2311,6 +2311,16 @@ static void drain_local_stock(struct work_struct *dummy)
obj_cgroup_put(old);
}
+static noinline void drain_stock_1(struct memcg_stock_pcp *stock)
+{
+ drain_stock(stock);
+}
+
+static noinline void drain_stock_2(struct memcg_stock_pcp *stock)
+{
+ drain_stock(stock);
+}
+
/*
* Cache charges(val) to local per_cpu area.
* This will be consumed by consume_stock() function, later.
@@ -2321,14 +2331,14 @@ static void __refill_stock(struct mem_cgroup *memcg, unsigned int nr_pages)
stock = this_cpu_ptr(&memcg_stock);
if (READ_ONCE(stock->cached) != memcg) { /* reset if necessary */
- drain_stock(stock);
+ drain_stock_1(stock);
css_get(&memcg->css);
WRITE_ONCE(stock->cached, memcg);
}
stock->nr_pages += nr_pages;
if (stock->nr_pages > MEMCG_CHARGE_BATCH)
- drain_stock(stock);
+ drain_stock_2(stock);
}
static void refill_stock(struct mem_cgroup *memcg, unsigned int nr_pages)
--
2.40.1.606.ga4b1b128d6-goog
next prev parent reply other threads:[~2023-05-11 21:18 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230508020801.10702-1-cathy.zhang@intel.com>
[not found] ` <20230508020801.10702-2-cathy.zhang@intel.com>
2023-05-09 17:19 ` Shakeel Butt
2023-05-09 18:04 ` Chen, Tim C
2023-05-09 18:17 ` Shakeel Butt
2023-05-10 7:03 ` Zhang, Cathy
2023-05-10 7:32 ` Zhang, Cathy
[not found] ` <3887b08ac0e55e27a24d2f66afcfff1961ed9b13.camel@redhat.com>
[not found] ` <CH3PR11MB73459006FCE3887E1EA3B82FFC769@CH3PR11MB7345.namprd11.prod.outlook.com>
[not found] ` <CH3PR11MB73456D792EC6E7614E2EF14DFC769@CH3PR11MB7345.namprd11.prod.outlook.com>
[not found] ` <CANn89iL6Ckuu9vOEvc7A9CBLGuh-EpbwFRxRAchV-6VFyhTUpg@mail.gmail.com>
[not found] ` <CH3PR11MB73458BB403D537CFA96FD8DDFC769@CH3PR11MB7345.namprd11.prod.outlook.com>
[not found] ` <CANn89iJvpgXTwGEiXAkFwY3j3RqVhNzJ_6_zmuRb4w7rUA_8Ug@mail.gmail.com>
2023-05-09 16:09 ` Shakeel Butt
2023-05-10 6:54 ` Zhang, Cathy
2023-05-10 11:11 ` Zhang, Cathy
2023-05-10 11:24 ` Eric Dumazet
2023-05-10 13:52 ` Zhang, Cathy
2023-05-10 15:07 ` Eric Dumazet
2023-05-10 16:09 ` Zhang, Cathy
2023-05-10 19:00 ` Shakeel Butt
2023-05-11 0:53 ` Zhang, Cathy
2023-05-11 6:59 ` Zhang, Cathy
2023-05-11 7:50 ` Eric Dumazet
2023-05-11 9:26 ` Zhang, Cathy
2023-05-11 16:23 ` Shakeel Butt
2023-05-11 16:35 ` Eric Dumazet
2023-05-11 17:10 ` Shakeel Butt
2023-05-11 21:18 ` Shakeel Butt [this message]
2023-05-12 2:38 ` Zhang, Cathy
2023-05-12 3:23 ` Zhang, Cathy
2023-05-12 5:06 ` Shakeel Butt
2023-05-12 5:51 ` Zhang, Cathy
2023-05-12 17:17 ` Shakeel Butt
2023-05-15 3:46 ` Zhang, Cathy
2023-05-15 4:13 ` Shakeel Butt
2023-05-15 6:27 ` Zhang, Cathy
2023-05-15 19:50 ` Shakeel Butt
2023-05-16 5:46 ` Oliver Sang
2023-05-17 16:24 ` Shakeel Butt
2023-05-17 16:33 ` Eric Dumazet
2023-05-17 17:04 ` Shakeel Butt
2023-07-28 2:26 ` Zhang, Cathy
2023-05-19 2:53 ` Oliver Sang
2023-05-31 8:46 ` Oliver Sang
2023-05-09 17:58 ` Shakeel Butt
2023-05-10 7:21 ` Zhang, Cathy
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=20230511211338.oi4xwoueqmntsuna@google.com \
--to=shakeelb@google.com \
--cc=Brandeburg@google.com \
--cc=Chen@google.com \
--cc=Srinivas@google.com \
--cc=You@google.com \
--cc=Zhang@google.com \
--cc=cathy.zhang@intel.com \
--cc=cgroups@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizhen.you@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=suresh.srinivas@intel.com \
--cc=tim.c.chen@intel.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