From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Radu Stoenescu <radu.stoe@gmail.com>
Cc: Jesper Dangaard Brouer <brouer@redhat.com>,
Jason Wang <jasowang@redhat.com>,
"xdp-newbies@vger.kernel.org" <xdp-newbies@vger.kernel.org>,
simon.horman@netronome.com
Subject: Re: Redirect from NIC to TAP
Date: Tue, 9 Feb 2021 10:41:37 +0100 [thread overview]
Message-ID: <20210209094137.GA14290@ranger.igk.intel.com> (raw)
In-Reply-To: <CAM-scZNLN5cgJBEdVFSSrLJi3zW-5THzbY=diESdKiiisCT9MQ@mail.gmail.com>
On Tue, Feb 09, 2021 at 11:26:06AM +0200, Radu Stoenescu wrote:
> Hello
>
> My physical NIC is a Netronome (I can come back with exact model type
> and driver version).
>
> Redirect NIC to TAP doesn't work when XDP is attached in driver mode.
> It works when they are both in generic mode. I haven't tried other
> combinations of attachment modes (one driver, other generic etc.).
Looks like Netronome driver still doesn't support XDP_REDIRECT in native
mode.
CC: Simon
Simon, any plans on adding support for redirect?
>
> Thanks
>
> On Tue, Feb 9, 2021 at 11:21 AM Jesper Dangaard Brouer
> <brouer@redhat.com> wrote:
> >
> > On Tue, 9 Feb 2021 10:31:50 +0200
> > Radu Stoenescu <radu.stoe@gmail.com> wrote:
> >
> > > Is it possible to redirect packets from XDP program attached in driver
> > > mode to a physical NIC to a TAP interface?
> >
> > Cc. Jason Wang as I think he implemented this, but I'm not 100% sure.
> > Maybe Jason can remember?
> > (or point me to the relevant code that I can check).
> >
> > > The same works fine if the XDP programs are attached in generic mode.
> >
> > So, you have tried and it doesn't work.
> >
> > What is your setup?
> >
> > --
> > Best regards,
> > Jesper Dangaard Brouer
> > MSc.CS, Principal Kernel Engineer at Red Hat
> > LinkedIn: http://www.linkedin.com/in/brouer
> >
>
>
> --
> Radu Stoenescu
next prev parent reply other threads:[~2021-02-09 9:53 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 [this message]
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
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=20210209094137.GA14290@ranger.igk.intel.com \
--to=maciej.fijalkowski@intel.com \
--cc=brouer@redhat.com \
--cc=jasowang@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.