From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Christian Deacon <gamemann@gflclan.com>
Cc: brouer@redhat.com, xdp-newbies@vger.kernel.org
Subject: Re: Measuring/Debugging XDP Performance
Date: Thu, 23 Jan 2020 14:11:22 +0100 [thread overview]
Message-ID: <20200123141122.3783e298@carbon> (raw)
In-Reply-To: <6c3dc8ff-e2bd-a06e-d9f0-c5be0103d266@gflclan.com>
On Wed, 22 Jan 2020 12:02:23 -0600
Christian Deacon <gamemann@gflclan.com> wrote:
> Hey everyone,
>
> I am new to XDP + AF_XDP (along with C programming in general), but I am
> very interested in it and I've been learning a lot recently. I own an
> Anycast network and our POP servers are running custom software our
> developer created that processes packets using XDP. This software
> basically forwards specific traffic to another machine via an IPIP
> tunnel.
Why are you using AF_XDP to implement a simple IPIP tunnel header?
You can easily implement it in BPF.
Example here:
https://github.com/torvalds/linux/blob/master/samples/bpf/xdp_tx_iptunnel_kern.c#L110-L112
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2020-01-23 13:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 18:02 Measuring/Debugging XDP Performance Christian Deacon
2020-01-22 22:11 ` Vincent Li
2020-01-23 12:30 ` Jesper Dangaard Brouer
2020-01-23 13:11 ` Jesper Dangaard Brouer [this message]
2020-01-23 17:22 ` Christian Deacon
2020-01-23 20:38 ` Jesper Dangaard Brouer
2020-01-23 21:38 ` Christian Deacon
2020-01-28 18:55 ` Christian Deacon
2020-01-29 1:19 ` Matheus Salgueiro Castanho
[not found] ` <b1d478e6-555c-97da-f967-4f10f879f589@gflclan.com>
2020-01-29 12:09 ` Jesper Dangaard Brouer
2020-01-29 14:26 ` Jesper Dangaard Brouer
2020-01-30 14:53 ` Christian Deacon
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=20200123141122.3783e298@carbon \
--to=brouer@redhat.com \
--cc=gamemann@gflclan.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.