[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a87c2f7f-a601-7b91-9bc5-aff22ec51d62@redhat.com>
Date: Tue, 5 Apr 2022 14:18:29 +0200
From: Jesper Dangaard Brouer <jbrouer@...hat.com>
To: Maciej Fijalkowski <maciej.fijalkowski@...el.com>,
bpf@...r.kernel.org, ast@...nel.org, daniel@...earbox.net,
magnus.karlsson@...el.com, bjorn@...nel.org
Cc: brouer@...hat.com, netdev@...r.kernel.org, maximmi@...dia.com,
alexandr.lobakin@...el.com
Subject: Re: [PATCH bpf-next 01/10] xsk: improve xdp_do_redirect() error codes
On 05/04/2022 13.06, Maciej Fijalkowski wrote:
> From: Björn Töpel<bjorn@...nel.org>
>
> The error codes returned by xdp_do_redirect() when redirecting a frame
> to an AF_XDP socket has not been very useful. A driver could not
> distinguish between different errors. Prior this change the following
> codes where used:
>
> Socket not bound or incorrect queue/netdev: EINVAL
> XDP frame/AF_XDP buffer size mismatch: ENOSPC
> Could not allocate buffer (copy mode): ENOSPC
> AF_XDP Rx buffer full: ENOSPC
>
> After this change:
>
> Socket not bound or incorrect queue/netdev: EINVAL
> XDP frame/AF_XDP buffer size mismatch: ENOSPC
> Could not allocate buffer (copy mode): ENOMEM
> AF_XDP Rx buffer full: ENOBUFS
>
> An AF_XDP zero-copy driver can now potentially determine if the
> failure was due to a full Rx buffer, and if so stop processing more
> frames, yielding to the userland AF_XDP application.
>
> Signed-off-by: Björn Töpel<bjorn@...nel.org>
> Signed-off-by: Maciej Fijalkowski<maciej.fijalkowski@...el.com>
Acked-by: Jesper Dangaard Brouer <brouer@...hat.com>
Thanks for picking this work up again! :-)
--Jesper
Powered by blists - more mailing lists