Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp1357713pxf; Fri, 19 Mar 2021 05:38:09 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy4vCRMGxy7tog6Im+ffnK7tUGgJbsQahmdM61yOKdRnvh7EfMv7KLmpRGxAZyKveF1WsV2 X-Received: by 2002:a17:907:2513:: with SMTP id y19mr4045840ejl.241.1616157489716; Fri, 19 Mar 2021 05:38:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616157489; cv=none; d=google.com; s=arc-20160816; b=WOggUOdih5FXSxoKb0zoSF35oMqk747IA4oRw5NWDWjLDrtZT6Y+6YnaXO/KZdNo6l n3zn+G0NnrcsEzlxVQG5ioZXs0vo8otA5OdRaGLJZJa3nhkkubv1iSUfWGb49YZhIiu3 Zs+HlgRSSNOC6heXv5j4Fq10oIKAjigcMZC7bmVRTNiMCSlmFnG45NYLjcf6k35M7kTD emglHRZc826ODR3wS0zVZoMAzO/nHey0WZzTvhuTzt4nuIYsU91aix+SYNzr+dQ5HbJz 04M9ZYDZwmVAPZBaWarnp6giE4/BFHkZ162KFeeJihUlwROPEZi4Arqnql3XLBe4d1zE /Mow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id:dkim-signature; bh=sswxe4rRhgVUvSlq2Qd1m3JvsgJC65o2sDRzUfVqiS4=; b=PX73R3uT3g8ECcP2fYTPDepz0iw/8jUz87/LL2IewkcYxZNyqRY5zmZeyWA74M2hUM bcjA9GrOm6NDnibXZOnch/EbZeuWo5lWo8uBOxyI1mONPdTMLahhyc2V76aSkgZ0gofi Lc/54QUrs84vpK+rU+KIhneD+bdm2vEuyLhz9H6AdfXTA+hPVKT+Gv7Yu6MoCX5sx6N6 4FBIDmv5Q6ZPZgaKrInj62pB34FRFsScDdXNJe5RJkXJYuixGhL7bcCEz4tYVzIwouNS K65E2kLALicCaWuthG+Euqx08BLBfAkk+BEReQy46sGWKVOKWdCkZunQPEMdM26vR/4w uGYw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=CUudqu9M; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s10si4210736edi.563.2021.03.19.05.37.47; Fri, 19 Mar 2021 05:38:09 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=CUudqu9M; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229979AbhCSMgU (ORCPT + 99 others); Fri, 19 Mar 2021 08:36:20 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:50439 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229805AbhCSMfv (ORCPT ); Fri, 19 Mar 2021 08:35:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1616157351; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=sswxe4rRhgVUvSlq2Qd1m3JvsgJC65o2sDRzUfVqiS4=; b=CUudqu9MGiwGZSajOmB67h7MrLI+Hk5YcksZQqttfz0A3XwxUgFCxHWGZXuqmh8qkUkCGn FcVUBxmYJ4K/XN2M+otcZzUb1MC56KvSj2n21w4Zl2/E0I7RPlxS7g+sN5/MECNeyl7nTr GZxw3ykG0+jLiDWvEX0r8VzF2/FqTEI= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-599-aXZNWhFAN62xOshD1dqoig-1; Fri, 19 Mar 2021 08:35:47 -0400 X-MC-Unique: aXZNWhFAN62xOshD1dqoig-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 7671F87A83A; Fri, 19 Mar 2021 12:35:45 +0000 (UTC) Received: from ovpn-112-226.ams2.redhat.com (ovpn-112-226.ams2.redhat.com [10.36.112.226]) by smtp.corp.redhat.com (Postfix) with ESMTP id E436C5D9C6; Fri, 19 Mar 2021 12:35:42 +0000 (UTC) Message-ID: <5c1fce37033e98e483728ea9879c3cf4ae83aa28.camel@redhat.com> Subject: Re: [PATCH net-next 2/4] gro: add combined call_gro_receive() + INDIRECT_CALL_INET() helper From: Paolo Abeni To: Alexander Lobakin Cc: "David S. Miller" , Jakub Kicinski , Mauro Carvalho Chehab , Kirill Tkhai , Bartosz Golaszewski , Leon Romanovsky , Eric Dumazet , netdev@vger.kernel.org, linux-kernel@vger.kernel.org Date: Fri, 19 Mar 2021 13:35:41 +0100 In-Reply-To: <20210319114300.108808-1-alobakin@pm.me> References: <20210318184157.700604-1-alobakin@pm.me> <20210318184157.700604-3-alobakin@pm.me> <1ebd301832ff86cc414dd17eee0b3dfc91ff3c08.camel@redhat.com> <20210319111315.3069-1-alobakin@pm.me> <20210319114300.108808-1-alobakin@pm.me> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2021-03-19 at 11:43 +0000, Alexander Lobakin wrote: > I'm not sure if you did it on purpose in commit aaa5d90b395a7 > ("net: use indirect call wrappers at GRO network layer"). > Was that intentional I must admit that 2y+ later my own intentions are not so clear to me too;) > for the sake of more optimized path for the > kernels with moduled IPv6, Uhm... no I guess that was more an underlook on my side. > or I can replace INDIRECT_CALL_INET() > with INDIRECT_CALL_2() here too? If that build with IPV6=nmy, I would say yes. > I want to keep GRO callbacks that > make use of indirect call wrappers unified. L4 will still need some special handling as ipv6 udp gro callbacks are not builtin with CONFIG_IPV6=m :( Cheers, Paolo