[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87cygvj4xo.fsf@toke.dk>
Date: Thu, 09 Jan 2025 18:02:59 +0100
From: Toke Høiland-Jørgensen <toke@...hat.com>
To: Alexander Lobakin <aleksander.lobakin@...el.com>, Jesper Dangaard Brouer
<hawk@...nel.org>
Cc: Andrew Lunn <andrew+netdev@...n.ch>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski
<kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Lorenzo Bianconi
<lorenzo@...nel.org>, Daniel Xu <dxu@...uu.xyz>, Alexei Starovoitov
<ast@...nel.org>, Daniel Borkmann <daniel@...earbox.net>, Andrii Nakryiko
<andrii@...nel.org>, John Fastabend <john.fastabend@...il.com>, Martin
KaFai Lau <martin.lau@...ux.dev>, netdev@...r.kernel.org,
bpf@...r.kernel.org, linux-kernel@...r.kernel.org, Jesse Brandeburg
<jbrandeburg@...udflare.com>, kernel-team <kernel-team@...udflare.com>
Subject: Re: [PATCH net-next v2 0/8] bpf: cpumap: enable GRO for XDP_PASS
frames
Alexander Lobakin <aleksander.lobakin@...el.com> writes:
>> What is the "small frame" size being used?
>
> xdp-trafficgen currently hardcodes frame sizes to 64 bytes. I was
> planning to add an option to configure frame size and send it upstream,
> but never finished it yet unfortunately.
Well, I guess I can be of some help here. Just pushed an update to
xdp-trafficgen to support specifying the packet size :)
-Toke
Powered by blists - more mailing lists