From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Radu Stoenescu <radu.stoe@gmail.com>,
Simon Horman <simon.horman@netronome.com>
Cc: Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
Jesper Dangaard Brouer <brouer@redhat.com>,
Jason Wang <jasowang@redhat.com>,
"xdp-newbies@vger.kernel.org" <xdp-newbies@vger.kernel.org>
Subject: Re: Redirect from NIC to TAP
Date: Mon, 01 Mar 2021 17:20:40 +0100 [thread overview]
Message-ID: <87eegyx2uf.fsf@toke.dk> (raw)
In-Reply-To: <CAM-scZPjB4QFTNPfbzD0DNmrfKMKUPMnnH+gSRFRk6jH4_WswA@mail.gmail.com>
Radu Stoenescu <radu.stoe@gmail.com> writes:
> Thanks a lot for the info.
>
> In retrospect, was there a way I could reach this conclusion myself
> (no driver support)? I'm asking this since I'm relatively new to the
> environment and we run various NICs from various vendors, and I would
> like to know how to perform the "due diligence" myself before reaching
> out?
Grepping the source code is one. The xdp_monitor tool from samples/bpf
might have provided a hint as well, but only that something was wrong,
not the cause.
This is a long-standing issue, and there's been some discussion around
it, but let's just say that no consensus has emerged yet :/
-Toke
next prev parent reply other threads:[~2021-03-01 16:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 8:31 Redirect from NIC to TAP Radu Stoenescu
2021-02-09 9:21 ` Jesper Dangaard Brouer
2021-02-09 9:26 ` Radu Stoenescu
2021-02-09 9:41 ` Maciej Fijalkowski
2021-02-10 4:30 ` David Ahern
2021-02-18 10:12 ` Simon Horman
2021-02-28 6:55 ` Radu Stoenescu
2021-03-01 16:20 ` Toke Høiland-Jørgensen [this message]
2021-02-10 3:42 ` Jason Wang
2021-02-10 11:35 ` Jesper Dangaard Brouer
2021-02-18 5:48 ` Jason Wang
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eegyx2uf.fsf@toke.dk \
--to=toke@redhat.com \
--cc=brouer@redhat.com \
--cc=jasowang@redhat.com \
--cc=maciej.fijalkowski@intel.com \
--cc=radu.stoe@gmail.com \
--cc=simon.horman@netronome.com \
--cc=xdp-newbies@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).