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 94691C64EC4 for ; Fri, 10 Mar 2023 07:41:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230398AbjCJHlj (ORCPT ); Fri, 10 Mar 2023 02:41:39 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35930 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230389AbjCJHkv (ORCPT ); Fri, 10 Mar 2023 02:40:51 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A742F104922; Thu, 9 Mar 2023 23:40:23 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 4C6ECB821DF; Fri, 10 Mar 2023 07:40:22 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id 00BDDC4331D; Fri, 10 Mar 2023 07:40:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1678434021; bh=aMCZFZWpmUkhd0ND1FCMjMn88Z7Y4ZjzuCO60/lYc4A=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=D4jumGUIuPDqMysUrmpKCWrQc2eYJPyIatStLlcvumrOQEh8lxhAHL5KytRr+KSXb 5eIp1vu5JuUu4FTPA+l0Jl0SnZtOkagZD9XyA/Cw782FwiPta9eoRQlZARgYi/6exA Irb2++tOB/76Ma08X2hBfvQ3uphOG6pCu2gyEdPgcyPFgltvmUybu7Gv/RsvwVF0gv 25fjKTgBuGzRiHDvV1VPchbi+pBWJbjXn0E5p1JGLa9IWckZBNutmHOsupew+KV3ms 8kI7nkQjqU8NRCkCiMO7BumjfSTwyhgOj6ccrcgjau0WflVZQ6ImRlRA5Y/3d4MC4E BrXWXEzR4Y6IA== Received: from aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (localhost.localdomain [127.0.0.1]) by aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (Postfix) with ESMTP id D6DE6E270C7; Fri, 10 Mar 2023 07:40:20 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [PATCH v4 net-next] udp: introduce __sk_mem_schedule() usage From: patchwork-bot+netdevbpf@kernel.org Message-Id: <167843402087.26917.6747945848629021248.git-patchwork-notify@kernel.org> Date: Fri, 10 Mar 2023 07:40:20 +0000 References: <20230308021153.99777-1-kerneljasonxing@gmail.com> In-Reply-To: <20230308021153.99777-1-kerneljasonxing@gmail.com> To: Jason Xing Cc: simon.horman@corigine.com, willemdebruijn.kernel@gmail.com, davem@davemloft.net, dsahern@kernel.org, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, bpf@vger.kernel.org, kernelxing@tencent.com Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello: This patch was applied to netdev/net-next.git (main) by Jakub Kicinski : On Wed, 8 Mar 2023 10:11:53 +0800 you wrote: > From: Jason Xing > > Keep the accounting schema consistent across different protocols > with __sk_mem_schedule(). Besides, it adjusts a little bit on how > to calculate forward allocated memory compared to before. After > applied this patch, we could avoid receive path scheduling extra > amount of memory. > > [...] Here is the summary with links: - [v4,net-next] udp: introduce __sk_mem_schedule() usage https://git.kernel.org/netdev/net-next/c/fd9c31f83441 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html