From: Jesper Dangaard Brouer <brouer@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: christina.jacob.koikara@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Sunil.Goutham@cavium.com,
Christina.Jacob@cavium.com, brouer@redhat.com
Subject: Re: [PATCH v4 1/1] xdp: Sample xdp program implementing ip forward
Date: Thu, 9 Nov 2017 02:38:06 +0100 [thread overview]
Message-ID: <20171109023806.36b38f0c@redhat.com> (raw)
In-Reply-To: <20171108.104024.315386187840767748.davem@davemloft.net>
On Wed, 08 Nov 2017 10:40:24 +0900 (KST)
David Miller <davem@davemloft.net> wrote:
> From: Christina Jacob <christina.jacob.koikara@gmail.com>
> Date: Sun, 5 Nov 2017 08:52:30 +0530
>
> > From: Christina Jacob <Christina.Jacob@cavium.com>
> >
> > Implements port to port forwarding with route table and arp table
> > lookup for ipv4 packets using bpf_redirect helper function and
> > lpm_trie map.
> >
> > Signed-off-by: Christina Jacob <Christina.Jacob@cavium.com>
>
> Applied to net-next, thank you.
I've not had time to proper test (and review) this V4 patch, but I
guess I'll have to do so when I get home from Seoul...
I especially want to measure the effect of using bpf_redirect_map().
To Christina: what performance improvement did you see on your
board/arch when switching from bpf_redirect() to bpf_redirect_map()?
--
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-11-09 1:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-05 3:22 [PATCH v4 0/1] XDP program for ip forward Christina Jacob
2017-11-05 3:22 ` [PATCH v4 1/1] xdp: Sample xdp program implementing " Christina Jacob
2017-11-08 1:40 ` David Miller
2017-11-09 1:38 ` Jesper Dangaard Brouer [this message]
2017-11-15 3:07 ` 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=20171109023806.36b38f0c@redhat.com \
--to=brouer@redhat.com \
--cc=Christina.Jacob@cavium.com \
--cc=Sunil.Goutham@cavium.com \
--cc=christina.jacob.koikara@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 NNTP newsgroup(s).