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 26F61C433FE for ; Wed, 27 Apr 2022 22:48:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234208AbiD0WwB (ORCPT ); Wed, 27 Apr 2022 18:52:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58402 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231531AbiD0WwA (ORCPT ); Wed, 27 Apr 2022 18:52:00 -0400 Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F2F9089CED for ; Wed, 27 Apr 2022 15:48:46 -0700 (PDT) Received: by mail-lf1-x130.google.com with SMTP id p10so5554797lfa.12 for ; Wed, 27 Apr 2022 15:48:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=openvz-org.20210112.gappssmtp.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=SQk+uPdXjus9l+tZCRcT7jspmYgklYtunIPDK1R0FPo=; b=4be664J+OKOeBO0o8b8/lSmk7jn8HmLIxoeRFfTKVZp/qfcuXsj0nn0H7AsnMzYhl1 ES/5EofZCQG+lU25D5qAXkc8AWQpCGUfz9nDBy6CFgdN3kWmzPKWPX3ouImm0xjv8Hot Q1nLzcRXHoGKjZZq2Ugu0RFU8yN4C0APkgUeDUB6KrZ1trEszX9xLoTyIm2bJLDwMNdk N7W3FgisFjh7vg/mDxMWbdPH84tzDYTOBZqlPWxH+fPixhU1X26YGN658TZN77CaspzE 6acX8xvHwftaEXxYqp5UMxc8oAGQBmwZm+vxqUqGmkQKqvGDa+d8noiqD3E455dFClQ1 3Wlw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=SQk+uPdXjus9l+tZCRcT7jspmYgklYtunIPDK1R0FPo=; b=bQwoHWV6Sg1nCCmz3Om9Dg2Hvjj7DBE2oPaDH26XKAE5JguJDMe7C+1/3Hobbrba9C k6DgEIHo8hU4Yet2geShWH90TsCpnJgtOGYsZ5V9/Uz2xQ8LK5npiJYyCx2wJvgOBXc8 u4PkBlj315SN3R3jhUfue7ClD+GI5p4/Tfo/BPM00e2ZM4mixFct5s6Tf6IvmScILVTR YtlJr8gW9tj08jwORi/4vHU0eTp1eaCGgRthwNLRt0LeoM6aPod2U4Txp7UT2gmQFIS+ 90HUgqyo6dt6x1d0qhVfEC9fzES3ZMSqOJbsyVuXjC/cPIdZn6YPhl2YLE/v943GEdsn NZNw== X-Gm-Message-State: AOAM531ueMVdhrPoiYdbix27LG7I6WS7Q9YWk2Z83CpCjvFsaVH8fVjt bkgT+2215PPQxLtlSfPXIf7Fiw== X-Google-Smtp-Source: ABdhPJz73JY3yLDUY6xr/jjV4y8SsKN6H0NWeoiwZQ6xAk04KGa1rAljireM7SzoraFwJvt6CG+IFw== X-Received: by 2002:a19:4f10:0:b0:471:fb4e:bf28 with SMTP id d16-20020a194f10000000b00471fb4ebf28mr16129205lfb.274.1651099725237; Wed, 27 Apr 2022 15:48:45 -0700 (PDT) Received: from [192.168.1.65] ([46.188.121.177]) by smtp.gmail.com with ESMTPSA id h10-20020ac24daa000000b00471f8c681fdsm1740502lfe.233.2022.04.27.15.48.44 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 27 Apr 2022 15:48:44 -0700 (PDT) Message-ID: <9600b84a-8590-4e7b-c74d-3f52fe905e7f@openvz.org> Date: Thu, 28 Apr 2022 01:48:43 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: [PATCH] memcg: enable accounting for veth queues Content-Language: en-US To: Jakub Kicinski Cc: Roman Gushchin , Vlastimil Babka , Shakeel Butt , kernel@openvz.org, linux-kernel@vger.kernel.org, Michal Hocko , cgroups@vger.kernel.org, netdev@vger.kernel.org, "David S. Miller" , Paolo Abeni References: <1c338b99-8133-6126-2ff2-94a4d3f26451@openvz.org> <20220427095854.79554fab@kernel.org> From: Vasily Averin In-Reply-To: <20220427095854.79554fab@kernel.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/27/22 19:58, Jakub Kicinski wrote: > On Wed, 27 Apr 2022 13:34:29 +0300 Vasily Averin wrote: >> Subject: [PATCH] memcg: enable accounting for veth queues > > This is a pure networking patch, right? The prefix should be "net: ", > I think. Thank you for the remark, I'll fix it. Initially it was a part of the patch accounted resources accounted when creating a new netdevice, but then I moved this piece to a separate patch, because unlike other cases, it is specific to veth. Thank you, Vasily Averin From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vasily Averin Subject: Re: [PATCH] memcg: enable accounting for veth queues Date: Thu, 28 Apr 2022 01:48:43 +0300 Message-ID: <9600b84a-8590-4e7b-c74d-3f52fe905e7f@openvz.org> References: <1c338b99-8133-6126-2ff2-94a4d3f26451@openvz.org> <20220427095854.79554fab@kernel.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=openvz-org.20210112.gappssmtp.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=SQk+uPdXjus9l+tZCRcT7jspmYgklYtunIPDK1R0FPo=; b=4be664J+OKOeBO0o8b8/lSmk7jn8HmLIxoeRFfTKVZp/qfcuXsj0nn0H7AsnMzYhl1 ES/5EofZCQG+lU25D5qAXkc8AWQpCGUfz9nDBy6CFgdN3kWmzPKWPX3ouImm0xjv8Hot Q1nLzcRXHoGKjZZq2Ugu0RFU8yN4C0APkgUeDUB6KrZ1trEszX9xLoTyIm2bJLDwMNdk N7W3FgisFjh7vg/mDxMWbdPH84tzDYTOBZqlPWxH+fPixhU1X26YGN658TZN77CaspzE 6acX8xvHwftaEXxYqp5UMxc8oAGQBmwZm+vxqUqGmkQKqvGDa+d8noiqD3E455dFClQ1 3Wlw== Content-Language: en-US In-Reply-To: <20220427095854.79554fab-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> List-ID: Content-Type: text/plain; charset="us-ascii" To: Jakub Kicinski Cc: Roman Gushchin , Vlastimil Babka , Shakeel Butt , kernel-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Michal Hocko , cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, "David S. Miller" , Paolo Abeni On 4/27/22 19:58, Jakub Kicinski wrote: > On Wed, 27 Apr 2022 13:34:29 +0300 Vasily Averin wrote: >> Subject: [PATCH] memcg: enable accounting for veth queues > > This is a pure networking patch, right? The prefix should be "net: ", > I think. Thank you for the remark, I'll fix it. Initially it was a part of the patch accounted resources accounted when creating a new netdevice, but then I moved this piece to a separate patch, because unlike other cases, it is specific to veth. Thank you, Vasily Averin