linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Zhang, Cathy" <cathy.zhang@intel.com>
To: Shakeel Butt <shakeelb@google.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" <Brandeburg@google.com>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
	"Srinivas, Suresh" <suresh.srinivas@intel.com>,
	"Chen, Tim C" <tim.c.chen@intel.com>,
	"You, 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: Mon, 15 May 2023 03:46:39 +0000	[thread overview]
Message-ID: <CH3PR11MB7345035086C1661BF5352E6EFC789@CH3PR11MB7345.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230512171702.923725-1-shakeelb@google.com>



> -----Original Message-----
> From: Shakeel Butt <shakeelb@google.com>
> Sent: Saturday, May 13, 2023 1:17 AM
> To: Zhang, Cathy <cathy.zhang@intel.com>
> Cc: Shakeel Butt <shakeelb@google.com>; Eric Dumazet
> <edumazet@google.com>; Linux MM <linux-mm@kvack.org>; Cgroups
> <cgroups@vger.kernel.org>; Paolo Abeni <pabeni@redhat.com>;
> davem@davemloft.net; kuba@kernel.org; Brandeburg@google.com;
> Brandeburg, Jesse <jesse.brandeburg@intel.com>; Srinivas, Suresh
> <suresh.srinivas@intel.com>; Chen, Tim C <tim.c.chen@intel.com>; You,
> Lizhen <lizhen.you@intel.com>; eric.dumazet@gmail.com;
> netdev@vger.kernel.org
> Subject: Re: [PATCH net-next 1/2] net: Keep sk->sk_forward_alloc as a proper
> size
> 
> On Fri, May 12, 2023 at 05:51:40AM +0000, Zhang, Cathy wrote:
> >
> >
> [...]
> > >
> > > Thanks a lot. This tells us that one or both of following scenarios
> > > are
> > > happening:
> > >
> > > 1. In the softirq recv path, the kernel is processing packets from
> > > multiple memcgs.
> > >
> > > 2. The process running on the CPU belongs to memcg which is
> > > different from the memcgs whose packets are being received on that CPU.
> >
> > Thanks for sharing the points, Shakeel! Is there any trace records you
> > want to collect?
> >
> 
> Can you please try the following patch and see if there is any improvement?

Hi Shakeel,

Try the following patch, the data of 'perf top' from system wide indicates that
the overhead of page_counter_cancel is dropped from 15.52% to 4.82%.

Without patch:
    15.52%  [kernel]            [k] page_counter_cancel
    12.30%  [kernel]            [k] page_counter_try_charge
    11.97%  [kernel]            [k] try_charge_memcg

With patch:
    10.63%  [kernel]            [k] page_counter_try_charge
     9.49%  [kernel]            [k] try_charge_memcg
     4.82%  [kernel]            [k] page_counter_cancel

The patch is applied on the latest net-next/main:
befcc1fce564 ("sfc: fix use-after-free in efx_tc_flower_record_encap_match()")

> 
> 
> From 48eb23c8cbb5d6c6086299c8a5ae4b3485c79a8c Mon Sep 17 00:00:00
> 2001
> From: Shakeel Butt <shakeelb@google.com>
> Date: Fri, 12 May 2023 17:04:35 +0000
> Subject: [PATCH] No batch charge in irq context
> 
> ---
>  mm/memcontrol.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c index
> d31fb1e2cb33..f1453a140fc8 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -2652,7 +2652,8 @@ void mem_cgroup_handle_over_high(void)  static
> int try_charge_memcg(struct mem_cgroup *memcg, gfp_t gfp_mask,
>  			unsigned int nr_pages)
>  {
> -	unsigned int batch = max(MEMCG_CHARGE_BATCH, nr_pages);
> +	unsigned int batch = in_task() ?
> +		max(MEMCG_CHARGE_BATCH, nr_pages) : nr_pages;
>  	int nr_retries = MAX_RECLAIM_RETRIES;
>  	struct mem_cgroup *mem_over_limit;
>  	struct page_counter *counter;
> --
> 2.40.1.606.ga4b1b128d6-goog


  reply	other threads:[~2023-05-15  3:46 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
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 [this message]
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=CH3PR11MB7345035086C1661BF5352E6EFC789@CH3PR11MB7345.namprd11.prod.outlook.com \
    --to=cathy.zhang@intel.com \
    --cc=Brandeburg@google.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=shakeelb@google.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