From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 70B193B29D for ; Fri, 11 Nov 2022 09:06:38 -0500 (EST) Received: by mail-pj1-x102a.google.com with SMTP id m14-20020a17090a3f8e00b00212dab39bcdso7880264pjc.0 for ; Fri, 11 Nov 2022 06:06:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=PKtyCbTmGhiBd9j8UR78u6926Sk5H+iLRouJAEq07Oo=; b=V66puYXy1oB+XyydALC6Rhl0MsU8z8LVKrep87BHFWieWAlPpBUbS+fw8uGjPXEFbp 5R56Uts9Mbwc3/XnoCqbPfVMiYfOMJ2pIGP/1Vv1g8nsNwVysJP21fzAEMgOFce2CR5g O+7zW9zIG+UqGipjl6dumx0wa1s+lHshTIAMJKVcwwQ7GylcZyumIobhDqHeACTNgFgC JsIz0/flKlQHPy6vg9asZcNo/uYzwO6PVtoQ48M4JbSLYoCS46wx1DMbSYDNrBUH+UQy x6WgtdwNNDcM5bAn7c1zhzuE9DuzHwsAl5tkVc8Rt0KJAeRLeR0OqqvywgVeduK7qnzv z1Qw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=PKtyCbTmGhiBd9j8UR78u6926Sk5H+iLRouJAEq07Oo=; b=4b61dnE1bSqEAaEyoJOZz7/7uRNhk5oADVNrlPHlYKMFqFSp2uZ5DxRSXgHnPKQWtC Mz5X0AhcD2Olswlv0Xw8WwMYYWm4xUTjlUTxTdH58Nq4qZi9SRjWnoyeRKH7HPHA1ZE9 HFnmgfq6DfGcwFapXFcCPeQNx3/zbTPsAf0vFymce3Gy0HkXbm4ec/zrdIBnhcxekdgF r3+amfmEyz/SOW95NZkoo8YddqwGjcY36Ydy4DkOxriM9sXLWmur+9Jba0jxPBKIGQKO lOZpqy3WXgo0K3H6CXq1/VVhsaiViwVDOE/OHo/FO+P4oNKpLVARcQ1DzfzgNThMjLX2 jLUg== X-Gm-Message-State: ANoB5plB8m3ISMWl0dKvPJ33heMAzAHjUAnv0wI8L0rIP/LGBPZUe2P9 1v0QuksJ8UNDJwBUTttObbNwDjex/ZBxwux/wZEvVKg9 X-Google-Smtp-Source: AA0mqf7+l276VdaH7KSNVf8ELL+ZDnk4XIG1ww7+4xKN8xz6/zWRLqiLnoeIfutUiLL9PVyG7dBHtBw4v5MdwHJIVMA= X-Received: by 2002:a17:90a:9748:b0:216:92a9:fca4 with SMTP id i8-20020a17090a974800b0021692a9fca4mr1925190pjw.245.1668175597055; Fri, 11 Nov 2022 06:06:37 -0800 (PST) MIME-Version: 1.0 References: <20221104032532.1615099-1-sdf@google.com> <20221104032532.1615099-7-sdf@google.com> <87k042xtkw.fsf@toke.dk> In-Reply-To: <87k042xtkw.fsf@toke.dk> From: Herbert Wolverson Date: Fri, 11 Nov 2022 08:06:26 -0600 Message-ID: Cc: libreqos Content-Type: multipart/alternative; boundary="000000000000e2b5d405ed326576" Subject: Re: [LibreQoS] Fwd: [RFC bpf-next v2 06/14] xdp: Carry over xdp metadata into skb context X-BeenThere: libreqos@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Many ISPs need the kinds of quality shaping cake can do List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Nov 2022 14:06:38 -0000 --000000000000e2b5d405ed326576 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable That looks like it could be very, very useful. There's more email thread there than I have time to read, I wonder if there's a way to chain the xdp metadata to secondary XDP programs (which would obviate a lot of the "doing everything repeatedly" problem when dissecting packets on the XDP side as well as when passing to the TC side of things). On Thu, Nov 10, 2022 at 5:45 PM Toke H=C3=B8iland-J=C3=B8rgensen via LibreQ= oS < libreqos@lists.bufferbloat.net> wrote: > Dave Taht via LibreQoS writes: > > > There is a long thread about xdp metadata going on here. I have high > > hopes for this concept once it lands, > > everything from getting the three hashes cake requires directly from > > the network card (and timestamps), but also a > > "quality" figure of some sort, and who knows what else... > > Haha, yeah, I actually mentioned LibreQoS as one of the use cases, here: > https://lore.kernel.org/r/87r0yaxw5s.fsf@toke.dk :) > > -Toke > _______________________________________________ > LibreQoS mailing list > LibreQoS@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/libreqos > --000000000000e2b5d405ed326576 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
That looks like it could be very, very useful. There&= #39;s more email thread there than I have time to read,
I wonder = if there's a way to chain the xdp metadata to secondary XDP programs (w= hich would
obviate a lot of the "doing everything repeatedly= " problem when dissecting packets on the XDP
side as well as= when passing to the TC side of things).

On Thu, Nov 10, 2022 at 5= :45 PM Toke H=C3=B8iland-J=C3=B8rgensen via LibreQoS <libreqos@lists.bufferbloat.net> wrot= e:
Dave Taht via= LibreQoS <libreqos@lists.bufferbloat.net> writes:

> There is a long thread about xdp metadata going on here. I have high > hopes for this concept once it lands,
> everything from getting the three hashes cake requires directly from > the network card (and timestamps), but also a
> "quality" figure of some sort, and who knows what else...
Haha, yeah, I actually mentioned LibreQoS as one of the use cases, here: https://lore.kernel.org/r/87r0yaxw5s.fsf@toke.dk= :)

-Toke
_______________________________________________
LibreQoS mailing list
LibreQo= S@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/libreqos
--000000000000e2b5d405ed326576--