XDP hardware hints discussion mail archive
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Tariq Toukan <ttoukan.linux@gmail.com>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Jesper Dangaard Brouer <brouer@redhat.com>,
	bpf <bpf@vger.kernel.org>,
	Network Development <netdev@vger.kernel.org>,
	Stanislav Fomichev <sdf@google.com>,
	Martin KaFai Lau <martin.lau@kernel.org>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Alexander Lobakin <alexandr.lobakin@intel.com>,
	Larysa Zaremba <larysa.zaremba@intel.com>,
	xdp-hints@xdp-project.net, anthony.l.nguyen@intel.com, "Song,
	Yoong Siang" <yoong.siang.song@intel.com>,
	"Ong, Boon Leong" <boon.leong.ong@intel.com>,
	intel-wired-lan <intel-wired-lan@lists.osuosl.org>,
	Paolo Abeni <pabeni@redhat.com>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	John Fastabend <john.fastabend@gmail.com>,
	Jesper Dangaard Brouer <hawk@kernel.org>,
	"David S. Miller" <davem@davemloft.net>
Subject: [xdp-hints] Re: [PATCH bpf V2] xdp: bpf_xdp_metadata use EOPNOTSUPP for no driver support
Date: Wed, 22 Mar 2023 11:34:21 -0700	[thread overview]
Message-ID: <CAADnVQ+AAiFPDkn0r9+1YAcjgLRoF63HspmcL2CQeqvQcHC57A@mail.gmail.com> (raw)
In-Reply-To: <682a413b-4f84-cc06-d378-3b44d721c64e@gmail.com>

On Tue, Mar 21, 2023 at 1:43 PM Tariq Toukan <ttoukan.linux@gmail.com> wrote:
>
>
>
> On 21/03/2023 15:52, Jesper Dangaard Brouer wrote:
> > When driver doesn't implement a bpf_xdp_metadata kfunc the fallback
> > implementation returns EOPNOTSUPP, which indicate device driver doesn't
> > implement this kfunc.
> >
> > Currently many drivers also return EOPNOTSUPP when the hint isn't
> > available, which is ambiguous from an API point of view. Instead
> > change drivers to return ENODATA in these cases.
> >
> > There can be natural cases why a driver doesn't provide any hardware
> > info for a specific hint, even on a frame to frame basis (e.g. PTP).
> > Lets keep these cases as separate return codes.
> >
> > When describing the return values, adjust the function kernel-doc layout
> > to get proper rendering for the return values.
> >
> > Fixes: ab46182d0dcb ("net/mlx4_en: Support RX XDP metadata")
> > Fixes: bc8d405b1ba9 ("net/mlx5e: Support RX XDP metadata")
> > Fixes: 306531f0249f ("veth: Support RX XDP metadata")
> > Fixes: 3d76a4d3d4e5 ("bpf: XDP metadata RX kfuncs")
> > Signed-off-by: Jesper Dangaard Brouer <brouer@redhat.com>
>
> For the mlx4/5 parts:
> Acked-by: Tariq Toukan <tariqt@nvidia.com>

FYI this patch was applied to bpf tree.

pw-bot doesn't notice bpf tree anymore :(

      reply	other threads:[~2023-03-22 18:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 13:52 [xdp-hints] " Jesper Dangaard Brouer
2023-03-21 18:41 ` [xdp-hints] " Stanislav Fomichev
2023-03-21 19:20 ` Toke Høiland-Jørgensen
2023-03-21 20:43 ` Tariq Toukan
2023-03-22 18:34   ` Alexei Starovoitov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.xdp-project.net/postorius/lists/xdp-hints.xdp-project.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAADnVQ+AAiFPDkn0r9+1YAcjgLRoF63HspmcL2CQeqvQcHC57A@mail.gmail.com \
    --to=alexei.starovoitov@gmail.com \
    --cc=alexandr.lobakin@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=ast@kernel.org \
    --cc=boon.leong.ong@intel.com \
    --cc=bpf@vger.kernel.org \
    --cc=brouer@redhat.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=john.fastabend@gmail.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=kuba@kernel.org \
    --cc=larysa.zaremba@intel.com \
    --cc=martin.lau@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@google.com \
    --cc=ttoukan.linux@gmail.com \
    --cc=xdp-hints@xdp-project.net \
    --cc=yoong.siang.song@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox