From: Michael Chan <michael.chan@broadcom.com>
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: "xdp-newbies@vger.kernel.org" <xdp-newbies@vger.kernel.org>,
"John Fastabend" <john.fastabend@gmail.com>,
"Daniel Borkmann" <borkmann@iogearbox.net>,
"Andy Gospodarek" <andy@greyhouse.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Paweł Staszewski" <pstaszewski@itcare.pl>
Subject: Re: XDP redirect measurements, gotchas and tracepoints
Date: Tue, 22 Aug 2017 11:02:27 -0700 [thread overview]
Message-ID: <CACKFLimAF9OYwz8EqG=1-N40hWuA-8C8k8ut0oFKYdduvZOxHA@mail.gmail.com> (raw)
In-Reply-To: <20170821212506.1cb0d5d6@redhat.com>
On Mon, Aug 21, 2017 at 12:25 PM, Jesper Dangaard Brouer
<brouer@redhat.com> wrote:
>
> I'be been playing with the latest XDP_REDIRECT feature, that was
> accepted in net-next (for ixgbe), see merge commit[1].
> [1] https://git.kernel.org/davem/net-next/c/6093ec2dc31
>
Just catching on XDP_REDIRECT and I have a very basic question. The
ingress device passes the XDP buffer to the egress device for XDP
redirect transmission. When the egress device has transmitted the
packet, is it supposed to just free the buffer? Or is it supposed to
be recycled?
In XDP_TX, the buffer is recycled back to the rx ring.
next prev parent reply other threads:[~2017-08-22 18:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 19:25 XDP redirect measurements, gotchas and tracepoints Jesper Dangaard Brouer
2017-08-21 22:35 ` Alexei Starovoitov
2017-08-22 6:37 ` Jesper Dangaard Brouer
2017-08-22 17:09 ` Alexei Starovoitov
2017-08-22 17:17 ` John Fastabend
2017-08-23 8:56 ` Jesper Dangaard Brouer
2017-08-22 18:02 ` Michael Chan [this message]
2017-08-22 18:17 ` John Fastabend
2017-08-22 18:30 ` Duyck, Alexander H
2017-08-22 20:04 ` Michael Chan
2017-08-23 1:06 ` Alexander Duyck
2017-08-23 6:59 ` Michael Chan
2017-08-23 8:29 ` Jesper Dangaard Brouer
2017-08-25 3:36 ` Michael Chan
2017-08-25 12:45 ` Jesper Dangaard Brouer
2017-08-25 15:10 ` John Fastabend
2017-08-25 15:28 ` Michael Chan
2017-08-28 16:02 ` Andy Gospodarek
2017-08-28 16:11 ` Alexander Duyck
2017-08-29 13:26 ` Jesper Dangaard Brouer
2017-08-29 16:23 ` Alexander Duyck
2017-08-29 19:02 ` Andy Gospodarek
2017-08-29 19:52 ` Alexander Duyck
2017-08-28 16:14 ` John Fastabend
2017-08-28 19:39 ` Andy Gospodarek
2017-08-23 14:51 ` Alexander Duyck
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='CACKFLimAF9OYwz8EqG=1-N40hWuA-8C8k8ut0oFKYdduvZOxHA@mail.gmail.com' \
--to=michael.chan@broadcom.com \
--cc=andy@greyhouse.net \
--cc=borkmann@iogearbox.net \
--cc=brouer@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pstaszewski@itcare.pl \
--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.