From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>
Cc: grygorii.strashko@ti.com, hawk@kernel.org, davem@davemloft.net,
ast@kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, xdp-newbies@vger.kernel.org,
netdev@vger.kernel.org, daniel@iogearbox.net,
jakub.kicinski@netronome.com, john.fastabend@gmail.com
Subject: Re: [PATCH net-next 0/3] net: ethernet: ti: cpsw: Add XDP support
Date: Fri, 24 May 2019 12:41:45 +0300 [thread overview]
Message-ID: <20190524094145.GA24675@apalos> (raw)
In-Reply-To: <20190523182035.9283-1-ivan.khoronzhuk@linaro.org>
Hi Ivan,
More XDP drivers, that's good!
> This patchset add XDP support for TI cpsw driver and base it on
> page_pool allocator. It was verified on af_xdp socket drop,
> af_xdp l2f, ebpf XDP_DROP, XDP_REDIRECT, XDP_PASS, XDP_TX.
>
> It was verified with following configs enabled:
> CONFIG_JIT=y
> CONFIG_BPFILTER=y
> CONFIG_BPF_SYSCALL=y
> CONFIG_XDP_SOCKETS=y
> CONFIG_BPF_EVENTS=y
> CONFIG_HAVE_EBPF_JIT=y
> CONFIG_BPF_JIT=y
> CONFIG_CGROUP_BPF=y
>
> Link on previous RFC:
> https://lkml.org/lkml/2019/4/17/861
>
The recycling pattern has changed i'll have a closer look in the weekend and let
you know
> Also regular tests with iperf2 were done in order to verify impact on
> regular netstack performance, compared with base commit:
> https://pastebin.com/JSMT0iZ4
Do you have any XDP related numbers?
>
> Based on net-next/master
>
> Ivan Khoronzhuk (3):
> net: ethernet: ti: davinci_cpdma: add dma mapped submit
> net: ethernet: ti: davinci_cpdma: return handler status
> net: ethernet: ti: cpsw: add XDP support
>
> drivers/net/ethernet/ti/Kconfig | 1 +
> drivers/net/ethernet/ti/cpsw.c | 570 +++++++++++++++++++++---
> drivers/net/ethernet/ti/cpsw_ethtool.c | 55 ++-
> drivers/net/ethernet/ti/cpsw_priv.h | 9 +-
> drivers/net/ethernet/ti/davinci_cpdma.c | 122 +++--
> drivers/net/ethernet/ti/davinci_cpdma.h | 6 +-
> drivers/net/ethernet/ti/davinci_emac.c | 18 +-
> 7 files changed, 675 insertions(+), 106 deletions(-)
>
> --
> 2.17.1
>
Thanks
/Ilias
prev parent reply other threads:[~2019-05-24 9:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 18:20 [PATCH net-next 0/3] net: ethernet: ti: cpsw: Add XDP support Ivan Khoronzhuk
2019-05-23 18:20 ` [PATCH net-next 1/3] net: ethernet: ti: davinci_cpdma: add dma mapped submit Ivan Khoronzhuk
2019-05-23 18:20 ` [PATCH net-next 2/3] net: ethernet: ti: davinci_cpdma: return handler status Ivan Khoronzhuk
2019-05-23 18:20 ` [PATCH net-next 3/3] net: ethernet: ti: cpsw: add XDP support Ivan Khoronzhuk
2019-05-24 11:05 ` Ilias Apalodimas
2019-05-27 18:21 ` Ivan Khoronzhuk
2019-05-24 11:54 ` Jesper Dangaard Brouer
2019-05-27 18:10 ` Ivan Khoronzhuk
2019-05-24 17:49 ` grygorii
2019-05-24 17:49 ` grygorii
2019-05-27 18:29 ` Ivan Khoronzhuk
2019-05-27 7:17 ` Dan Carpenter
2019-05-27 7:17 ` Dan Carpenter
2019-05-27 7:17 ` Dan Carpenter
2019-05-29 8:16 ` Jesper Dangaard Brouer
2019-05-29 9:58 ` Ivan Khoronzhuk
2019-05-24 9:41 ` Ilias Apalodimas [this message]
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=20190524094145.GA24675@apalos \
--to=ilias.apalodimas@linaro.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=grygorii.strashko@ti.com \
--cc=hawk@kernel.org \
--cc=ivan.khoronzhuk@linaro.org \
--cc=jakub.kicinski@netronome.com \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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.