From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0FB34C77B7E for ; Thu, 1 Jun 2023 09:22:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232769AbjFAJWI (ORCPT ); Thu, 1 Jun 2023 05:22:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42978 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232779AbjFAJWD (ORCPT ); Thu, 1 Jun 2023 05:22:03 -0400 Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D13B797 for ; Thu, 1 Jun 2023 02:21:37 -0700 (PDT) Received: by mail-pj1-x1033.google.com with SMTP id 98e67ed59e1d1-25669acf1b0so465421a91.0 for ; Thu, 01 Jun 2023 02:21:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bytedance.com; s=google; t=1685611297; x=1688203297; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=+SifIOg3EEC6zrsKMH+AeZTstzDtSY/mgHTMqEQiv+Y=; b=dPwWBIklySlVaBz8aeBqewiIOE0jlHpvIS+F8E+hS9vGXogaqy82OoWltppnH3cRu/ cyVh89Z0tPzL4LiipOoWMj4kULvV1bjyF1ODgZcwRTHTwQP4wrdSZClAe+2yEZO5k0KG +xy52vL/CfNLcNbysVWiRQd2lBmFYYGdgUkRcFn06ca4weGv8vtbQLFOD98a5NvIU1h8 3MMB9BB/QjJxePr73CbAcbJzyv86gEBsA3+TZogVj5nah9tD21ixe85Q43JaHlS5rvph JVLX9nxUx/CXzwXX6QAm7DNMOtv7MqwDiP8ypsAIRfUR7z3NRA2elUGaSxSyHZbcqIrK +lMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685611297; x=1688203297; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=+SifIOg3EEC6zrsKMH+AeZTstzDtSY/mgHTMqEQiv+Y=; b=dk6b40NRDGtsudaPBi948Fxbt3D2/KZCypoHNYYx1bM0w74GRVmHIp3o+AOtvPw/wU 69iqgCREII9aVl3TE7UBBbh+6ju0uPrIU0AbhGSuEexneIuD7pirRU+HCZvfuWyk6jP3 DIGUxMExH+7Ojl5cqnjZN6InKroZmMwXsWEBcvehFH785ysRglloF1gUp62+KPRO+/ri JCKXW1Qt3lJKpFMM0ozD8Fi8SFxYhWC44tY9diO50Kt+oBUiGKdU6JgZGT2/Ep57VGwG OX7uY/1iRpC9LkE1ld5kH1L/1EmytbWr1hluNLXl686FLYdM5qoHgB3ObwDFhMqrGMXc HE4w== X-Gm-Message-State: AC+VfDwsBiAMurVoOSdDzQf7kZhqgv3hEdHDFLphj0ALk/3o0WyCnO49 CvnhHRFnLX0Limf0tx7gajH0KQ== X-Google-Smtp-Source: ACHHUZ7FhBkJfqewCHGUAQxAW+IJu86mq8peHjHQfuAR1O2g96/sdIGSovJaGL9FEuFwpivR11EPMA== X-Received: by 2002:a17:90a:8a0b:b0:255:63ae:f940 with SMTP id w11-20020a17090a8a0b00b0025563aef940mr8215670pjn.36.1685611297358; Thu, 01 Jun 2023 02:21:37 -0700 (PDT) Received: from [10.94.58.170] ([203.208.167.147]) by smtp.gmail.com with ESMTPSA id h8-20020a17090a3d0800b00256bbfbabcfsm985328pjc.48.2023.06.01.02.21.31 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 01 Jun 2023 02:21:36 -0700 (PDT) Message-ID: <1fb805bc-baef-ee09-fa3a-d464af94751f@bytedance.com> Date: Thu, 1 Jun 2023 17:21:29 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.11.2 Subject: Re: Re: [PATCH v4 4/4] sock: Remove redundant cond of memcg pressure Content-Language: en-US To: Paolo Abeni , "David S . Miller" , Eric Dumazet , Jakub Kicinski , Johannes Weiner , Michal Hocko , Vladimir Davydov , Shakeel Butt , Muchun Song Cc: Simon Horman , netdev@vger.kernel.org, linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org References: <20230530114011.13368-1-wuyun.abel@bytedance.com> <20230530114011.13368-5-wuyun.abel@bytedance.com> From: Abel Wu In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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