From: brouer@redhat.com (Jesper Dangaard Brouer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] XDP Program for Ip forward
Date: Tue, 10 Oct 2017 15:12:31 +0200 [thread overview]
Message-ID: <20171010151231.69fde82f@redhat.com> (raw)
In-Reply-To: <1507620532-25804-1-git-send-email-Christina.Jacob@cavium.com>
On Tue, 10 Oct 2017 12:58:51 +0530 Christina Jacob <christina.jacob.koikara@gmail.com> wrote:
> The patch below implements port to port forwarding through route table and arp
> table lookup for ipv4 packets using bpf_redirect helper function and lpm_trie
> map. This has an improved performance over the normal kernel stack ip forward.
>
> Implementation details.
> -----------------------
[...]
>
> In the xdp3_user.c,
>
[...]
>
> In the xdp3_kern.c,
You forgot to update the program name in the cover letter.
> The array map for the 32 bit mask entries checked to see if there is a key that
> exactly matches with the destination ip. If it has a non zero destination mac
> entry then the xdp data is updated accordingly Otherwise a proper route and
> arp table lookup is done using the lpm_trie and the arp table array map.
>
> Usage: as ./xdp3 -S <ifindex1...ifindexn> (-S for
^^^^^
The executable name also changed.
> generic xdp implementation ifindex- the index of the interface to which
> the xdp program has to be attached.) in 4.14-rc3 kernel.
>
> Changes from v1 to v2
> ---------------------
>
> * As suggested by Jesper Dangaard Brouer
> 1. Changed the program name to list xdp_router_ipv4
Thanks
> 2. Changed the commandline arguments from ifindex list to interface name
> Usage : ./xdp_router_ipv4 [-S] <interface name list>
> -S for generic xdp implementation
> -interface name list is the list of interfaces to which
> the xdp program should attach to
Okay, you choose a slightly different way of implementing this, but it
shouldn't matter.
I'll try to test/benchmark your program...
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
WARNING: multiple messages have this Message-ID (diff)
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Christina Jacob <christina.jacob.koikara@gmail.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Sunil.Goutham@cavium.com,
daniel@iogearbox.net, dsahern@gmail.com,
Christina Jacob <Christina.Jacob@cavium.com>,
brouer@redhat.com
Subject: Re: [PATCH v2] XDP Program for Ip forward
Date: Tue, 10 Oct 2017 15:12:31 +0200 [thread overview]
Message-ID: <20171010151231.69fde82f@redhat.com> (raw)
In-Reply-To: <1507620532-25804-1-git-send-email-Christina.Jacob@cavium.com>
On Tue, 10 Oct 2017 12:58:51 +0530 Christina Jacob <christina.jacob.koikara@gmail.com> wrote:
> The patch below implements port to port forwarding through route table and arp
> table lookup for ipv4 packets using bpf_redirect helper function and lpm_trie
> map. This has an improved performance over the normal kernel stack ip forward.
>
> Implementation details.
> -----------------------
[...]
>
> In the xdp3_user.c,
>
[...]
>
> In the xdp3_kern.c,
You forgot to update the program name in the cover letter.
> The array map for the 32 bit mask entries checked to see if there is a key that
> exactly matches with the destination ip. If it has a non zero destination mac
> entry then the xdp data is updated accordingly Otherwise a proper route and
> arp table lookup is done using the lpm_trie and the arp table array map.
>
> Usage: as ./xdp3 -S <ifindex1...ifindexn> (-S for
^^^^^
The executable name also changed.
> generic xdp implementation ifindex- the index of the interface to which
> the xdp program has to be attached.) in 4.14-rc3 kernel.
>
> Changes from v1 to v2
> ---------------------
>
> * As suggested by Jesper Dangaard Brouer
> 1. Changed the program name to list xdp_router_ipv4
Thanks
> 2. Changed the commandline arguments from ifindex list to interface name
> Usage : ./xdp_router_ipv4 [-S] <interface name list>
> -S for generic xdp implementation
> -interface name list is the list of interfaces to which
> the xdp program should attach to
Okay, you choose a slightly different way of implementing this, but it
shouldn't matter.
I'll try to test/benchmark your program...
--
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:[~2017-10-10 13:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 7:28 [PATCH v2] XDP Program for Ip forward Christina Jacob
2017-10-10 7:28 ` Christina Jacob
2017-10-10 7:28 ` [PATCH v2] xdp: Sample xdp program implementing ip forward Christina Jacob
2017-10-10 7:28 ` Christina Jacob
2017-10-10 17:19 ` Stephen Hemminger
2017-10-10 17:19 ` Stephen Hemminger
2017-10-10 21:37 ` David Daney
2017-10-10 21:37 ` David Daney
2017-10-28 13:37 ` Christina Jacob
2017-10-28 13:37 ` Christina Jacob
2017-10-10 17:21 ` Stephen Hemminger
2017-10-10 17:21 ` Stephen Hemminger
2017-10-10 19:06 ` Jesper Dangaard Brouer
2017-10-10 19:06 ` Jesper Dangaard Brouer
2017-10-11 10:08 ` David Laight
2017-10-11 10:08 ` David Laight
2017-10-10 13:12 ` Jesper Dangaard Brouer [this message]
2017-10-10 13:12 ` [PATCH v2] XDP Program for Ip forward Jesper Dangaard Brouer
2017-10-10 14:00 ` Jesper Dangaard Brouer
2017-10-10 14:00 ` Jesper Dangaard Brouer
2017-10-11 17:06 ` Christina Jacob
2017-10-11 17:06 ` Christina Jacob
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=20171010151231.69fde82f@redhat.com \
--to=brouer@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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.