From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sin.source.kernel.org (sin.source.kernel.org [IPv6:2604:1380:40e1:4800::1]) by mail.toke.dk (Postfix) with ESMTPS id 82A329CDCF4 for ; Fri, 9 Dec 2022 23:13:12 +0100 (CET) Authentication-Results: mail.toke.dk; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=JSJHBySS 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 sin.source.kernel.org (Postfix) with ESMTPS id 13247CE2A59; Fri, 9 Dec 2022 22:13:07 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7EA98C433EF; Fri, 9 Dec 2022 22:13:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1670623985; bh=sWo6QnyRrnLIciflYfJb5Tz38EgC8oSkiMy96ny7pcs=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=JSJHBySSzQ7T/hhs06GIPYb2UxXmBePu9fG+WH7kkKPcYdvMLY15ODdYIu4vPzzoo KdXPUVyHw6aRk+nmjn49CmjEgiW5U0gRvYSucuKUwrYJkA8L7c9pOaviuMxMb/WcGt eaofScKt4Szz8P0FNCckGKKynnckllfXZxvTNELVUYBrno/5n5mp+v1HEvdOXoAAje 7knzUf1UYQhNSWwo3adiMqtj/9xe0E+u5DdrKyPPTTjfpl9+PvM+h5bxrb4Gm+3vs2 admm1EqnheyETz9CsG9Y0gi+LAo5uZ8AMXC3qrgYiR6x6wyhy5OD3fM7Vm8j8yOFnE jJsuimYq9nkXA== Date: Fri, 9 Dec 2022 14:13:03 -0800 From: Jakub Kicinski To: Stanislav Fomichev Message-ID: <20221209141303.3c3bbb7b@kernel.org> In-Reply-To: References: <20221206024554.3826186-1-sdf@google.com> <20221206024554.3826186-12-sdf@google.com> <875yellcx6.fsf@toke.dk> <87359pl9zy.fsf@toke.dk> <87tu25ju77.fsf@toke.dk> <87o7sdjt20.fsf@toke.dk> <87cz8sk59e.fsf@toke.dk> <20221209084524.01c09d9c@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-ID-Hash: IB7QPTOIJM5GXC4JHW26JKWHIJHSFETL X-Message-ID-Hash: IB7QPTOIJM5GXC4JHW26JKWHIJHSFETL X-MailFrom: kuba@kernel.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Toke =?UTF-8?B?SMO4aWxhbmQtSsO4cmdlbnNlbg==?= , Alexei Starovoitov , bpf , Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko , Martin KaFai Lau , Song Liu , Yonghong Song , John Fastabend , KP Singh , Hao Luo , Jiri Olsa , Saeed Mahameed , David Ahern , Willem de Bruijn , Jesper Dangaard Brouer , Anatoly Burakov , Alexander Lobakin , Magnus Karlsson , Maryam Tahhan , xdp-hints@xdp-project.net, Network Development X-Mailman-Version: 3.3.7 Precedence: list Subject: [xdp-hints] Re: [PATCH bpf-next v3 11/12] mlx5: Support RX XDP metadata List-Id: XDP hardware hints design discussion Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Fri, 9 Dec 2022 09:46:20 -0800 Stanislav Fomichev wrote: > > Is partial inlining hard? (inline just the check and generate a full > > call for the read, ending up with the same code as with _supported()) > > I'm assuming you're suggesting to do this partial inlining manually > (as in, writing the code to output this bytecode)? > This probably also falls into the "manual bpf asm generation tech debt" bucket? > LMK if I missed your point. Maybe just ignore that, I'm not sure how the unrolling of the _supported() calls was expected to work in the first place.