From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 52E0E3B29D for ; Fri, 11 Nov 2022 09:22:46 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1668176565; 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: in-reply-to:in-reply-to:references:references; bh=EaJcKWgafW0Br5UcVjJbOunlwjrMD0oq2RSM8x6WFq8=; b=eM5a8ML+dBSpTIZa4sVnQa2cklU9hq66K8zPuBe7n5EW5xs91Rc3GUdlDmxqEW9yt668WV XLnVI7TFDcRLcmcPK82im0zUzn8UyKN4wZVDdEx35yuRb7spyewz8jO5lGKw0IcmgKiFBj M32O1dKEbEyRFay7Bzj4hT/l3C3YXdw= Received: from mail-ed1-f71.google.com (mail-ed1-f71.google.com [209.85.208.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-298-94xNRf55Ndi23NRv2dPj5Q-1; Fri, 11 Nov 2022 09:22:44 -0500 X-MC-Unique: 94xNRf55Ndi23NRv2dPj5Q-1 Received: by mail-ed1-f71.google.com with SMTP id e15-20020a056402190f00b00461b0576620so3680724edz.2 for ; Fri, 11 Nov 2022 06:22:44 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:message-id:date:references:in-reply-to:subject:cc:to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=EaJcKWgafW0Br5UcVjJbOunlwjrMD0oq2RSM8x6WFq8=; b=BJyi8jBrkzzaceHiF3wQpXewASd6M1po6KVjZovCALPGkUo231dCS6txI1atlu/F6w NMKiwD7J0E6JtKCPbNXAJaao5m2DVG8MG+RpBuklOBtoN1lAgmcSg8a9VH0MFTaOkCZi /CbMd+FSQDOCwEb7WOB8OlOdivcEqF53Z/KepnNlNNV837nlCjY2a4hIFnXFfxQZyKzS Sh9tyHogaARsOLvYxc92EjDh7/6Tn4rOiiiZ4Zkg/YFsLeivfAdat6QnUS7klLV6jfUU dDfBYdyig2qgRpd2FC0JfcRpr3PxHSmy8b3Aor5jkDRNRaERtte2axkVPAWRrIIapFfN VesA== X-Gm-Message-State: ANoB5pnfHIgxxpjGD1qOw7dEWlqBRrCtczVcFrceyDTQSmyEd58wMTEO tDOsVkVKhgVdkgZ+kj/rqH7kBQ30L0z0w/URu9yEspOEbitCH+9cNzlarTZ721nlJoVJr42uAJG Wa801/fLJKBnCkJb3T5BM2bfDqkI= X-Received: by 2002:a05:6402:229b:b0:457:d794:f5ee with SMTP id cw27-20020a056402229b00b00457d794f5eemr1683700edb.227.1668176562925; Fri, 11 Nov 2022 06:22:42 -0800 (PST) X-Google-Smtp-Source: AA0mqf4NetwWv0AXw/vIeXUxyK5Vel6ygjWXgHLc2/ODllTt2yJinQm26OCfHe4bertg4XXZpQxdpg== X-Received: by 2002:a05:6402:229b:b0:457:d794:f5ee with SMTP id cw27-20020a056402229b00b00457d794f5eemr1683640edb.227.1668176561988; Fri, 11 Nov 2022 06:22:41 -0800 (PST) Received: from alrua-x1.borgediget.toke.dk ([2a0c:4d80:42:443::2]) by smtp.gmail.com with ESMTPSA id l27-20020a170906079b00b0073022b796a7sm934803ejc.93.2022.11.11.06.22.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 11 Nov 2022 06:22:41 -0800 (PST) Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id D091D7A6930; Fri, 11 Nov 2022 15:22:40 +0100 (CET) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= To: Herbert Wolverson Cc: libreqos In-Reply-To: References: <20221104032532.1615099-1-sdf@google.com> <20221104032532.1615099-7-sdf@google.com> <87k042xtkw.fsf@toke.dk> X-Clacks-Overhead: GNU Terry Pratchett Date: Fri, 11 Nov 2022 15:22:40 +0100 Message-ID: <87h6z5370v.fsf@toke.dk> MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Mailman-Approved-At: Fri, 11 Nov 2022 09:29:47 -0500 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:22:46 -0000 Herbert Wolverson via LibreQoS writes: > 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). Yeah, that is very much in scope; the metadata survives through multiple XDP programs even today (with libxdp) :) -Toke