[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1fb805bc-baef-ee09-fa3a-d464af94751f@bytedance.com>
Date: Thu, 1 Jun 2023 17:21:29 +0800
From: Abel Wu <wuyun.abel@...edance.com>
To: Paolo Abeni <pabeni@...hat.com>, "David S . Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Johannes Weiner <hannes@...xchg.org>,
Michal Hocko <mhocko@...nel.org>, Vladimir Davydov <vdavydov.dev@...il.com>,
Shakeel Butt <shakeelb@...gle.com>, Muchun Song <muchun.song@...ux.dev>
Cc: Simon Horman <simon.horman@...igine.com>, netdev@...r.kernel.org,
linux-mm@...ck.org, cgroups@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Re: [PATCH v4 4/4] sock: Remove redundant cond of memcg pressure
On 6/1/23 5:10 PM, Paolo Abeni wrote:
> On Tue, 2023-05-30 at 19:40 +0800, Abel Wu wrote:
>> Now with the previous patch, __sk_mem_raise_allocated() considers
>> the memory pressure of both global and the socket's memcg on a func-
>> wide level,
>
> Since the "previous patch" (aka "sock: Consider memcg pressure when
> raising sockmem") has been dropped in this series revision, I guess
> this patch should be dropped, too?
Yes indeed, these two patches should go together. Sorry for my
carelessness.
>
> Is this targeting the 'net-next' tree or the 'net' one? please specify
> the target tree into the subj line. I think we could consider net-next
> for this series, given the IMHO not trivial implications.
Got it, I will resend this series based on net-next.
Thanks!
Abel
Powered by blists - more mailing lists