From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out2.migadu.com (out2.migadu.com [IPv6:2001:41d0:2:aacc::]) by mail.toke.dk (Postfix) with ESMTPS id CE8969DCFE1 for ; Thu, 12 Jan 2023 19:20:36 +0100 (CET) Authentication-Results: mail.toke.dk; dkim=pass (1024-bit key; unprotected) header.d=linux.dev header.i=@linux.dev header.a=rsa-sha256 header.s=key1 header.b=hmnexZab Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1673547635; 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=6U+JSVqrc+yoFJl0Jg/9yO+ndlx7yLnVfK4r7uFQFIo=; b=hmnexZabVfr3zirdYk/mERR634FtyUBKRgCT4fndDYudcNWTOo6gss0YdBHh46ax1TL7Wz GypkmOlszR4TPvT7Ca1Bg8cWQo07kiFbFTvsvqvFF1t0P81YpUasVXPst1EAYQMPOFCGED DTloRTjnj1S3WDj6IetO/aNlKhIWOKc= Date: Thu, 12 Jan 2023 10:20:29 -0800 MIME-Version: 1.0 Content-Language: en-US To: Stanislav Fomichev , Tariq Toukan References: <20230112003230.3779451-1-sdf@google.com> <2f76e7d6-1771-a8f5-4bd1-6f7cd0b59173@gmail.com> X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Martin KaFai Lau In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT Message-ID-Hash: NI6QVJEXGTGKFRSHIIX3OONYMR5ZXAAU X-Message-ID-Hash: NI6QVJEXGTGKFRSHIIX3OONYMR5ZXAAU X-MailFrom: martin.lau@linux.dev 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: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org, song@kernel.org, yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org, haoluo@google.com, jolsa@kernel.org, David Ahern , Jakub Kicinski , Willem de Bruijn , Jesper Dangaard Brouer , Anatoly Burakov , Alexander Lobakin , Magnus Karlsson , Maryam Tahhan , Tariq Toukan , Saeed Mahameed , bpf@vger.kernel.org, xdp-hints@xdp-project.net, netdev@vger.kernel.org X-Mailman-Version: 3.3.7 Precedence: list Subject: [xdp-hints] Re: [PATCH bpf-next v7 00/17] xdp: hints via kfuncs List-Id: XDP hardware hints design discussion Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On 1/12/23 10:09 AM, Stanislav Fomichev wrote: > On Thu, Jan 12, 2023 at 12:19 AM Tariq Toukan wrote: >> >> >> >> On 12/01/2023 9:29, Martin KaFai Lau wrote: >>> On 1/11/23 4:32 PM, Stanislav Fomichev wrote: >>>> Please see the first patch in the series for the overall >>>> design and use-cases. >>>> >>>> See the following email from Toke for the per-packet metadata overhead: >>>> https://lore.kernel.org/bpf/20221206024554.3826186-1-sdf@google.com/T/#m49d48ea08d525ec88360c7d14c4d34fb0e45e798 >>>> >>>> Recent changes: >>>> >>>> - Bring back parts that were removed during patch reshuffling from "bpf: >>>> Introduce device-bound XDP programs" patch (Martin) >>>> >>>> - Remove netdev NULL check from __bpf_prog_dev_bound_init (Martin) >>>> >>>> - Remove netdev NULL check from bpf_dev_bound_resolve_kfunc (Martin) >>>> >>>> - Move target bound device verification from bpf_tracing_prog_attach into >>>> bpf_check_attach_target (Martin) >>>> >>>> - Move mlx5e_free_rx_in_progress_descs into txrx.h (Tariq) >>>> >>>> - mlx5e_fill_xdp_buff -> mlx5e_fill_mxbuf (Tariq) >>> >>> Thanks for the patches. The set lgtm. >>> >>> The selftest patch 11 and 17 have conflicts with the recent changes in >>> selftests/bpf/xsk.{h,c} and selftests/bpf/Makefile. eg. it no longer >>> needs XSK_LIBBPF_FLAGS__INHIBIT_PROG_LOAD, so please respin. From a >>> quick look, it should be some minor changes. >>> >>> Not sure if Tariq has a chance to look at the mlx5 changes shortly. The >>> set is getting pretty long and the core part is ready with veth and mlx4 >>> support. I think it is better to get the ready parts landed first such >>> that other drivers can also start adding support for it. One option is >>> to post the two mlx5 patches as another patchset and they can be >>> reviewed separately. >>> >> >> Hi, >> I posted new comments >> I think they can be handled quickly, and still be part of the next respin. >> >> I'm fine with both options though. You can keep the mlx5e patches or >> defer them to a followup series. Whatever works best for you. > > Either way is fine with me also. I can find some time today to address > Tariq's comments and respin if that works for everybody. Together SGTM also. Mentioned the option to separate and thought the core pieces can be landed faster than the mlx5 piece but it seems there is no major concern on the mlx5 changes.