From: Stephen Hemminger <stephen@networkplumber.org>
To: "Md. Islam" <mislam4@kent.edu>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
David Ahern <dsahern@gmail.com>,
agaceph@gmail.com, Pavel Emelyanov <xemul@openvz.org>,
Eric Dumazet <edumazet@google.com>,
alexei.starovoitov@gmail.com, brouer@redhat.com
Subject: Re: [PATCH v15 ] net/veth/XDP: Line-rate packet forwarding in kernel
Date: Mon, 2 Apr 2018 09:51:59 -0700 [thread overview]
Message-ID: <20180402095159.54c48aba@xeon-e3> (raw)
In-Reply-To: <CAFgPn1DX9cOpDRGj=wFwvZq_bpq6VFnEOzR1YbMuC0+=DFEWxA@mail.gmail.com>
On Sun, 1 Apr 2018 20:47:28 -0400
"Md. Islam" <mislam4@kent.edu> wrote:
> This patch implements IPv4 forwarding on xdp_buff. I added a new
> config option XDP_ROUTER. Kernel would forward packets through fast
> path when this option is enabled. But it would require driver support.
> Currently it only works with veth. Here I have modified veth such that
> it outputs xdp_buff. I created a testbed in Mininet. The Mininet
> script (topology.py) is attached. Here the topology is:
Having XDP routing would be great.
The solution you have chosen that by changing each driver does
not scale well since it requires lots of changes and is not ready
for upstream.
next prev parent reply other threads:[~2018-04-02 16:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 0:47 [PATCH v15 ] net/veth/XDP: Line-rate packet forwarding in kernel Md. Islam
2018-04-02 16:51 ` Stephen Hemminger [this message]
2018-04-02 18:03 ` John Fastabend
2018-04-02 18:09 ` David Ahern
2018-04-02 18:16 ` Alexei Starovoitov
2018-04-03 15:07 ` David Ahern
2018-04-03 16:41 ` John Fastabend
2018-04-03 16:45 ` David Miller
2018-04-03 17:00 ` David Ahern
2018-04-03 17:06 ` Alexei Starovoitov
2018-04-03 17:14 ` David Ahern
2018-04-03 17:37 ` Alexei Starovoitov
2018-04-04 1:09 ` David Ahern
2018-04-03 18:21 ` Jesper Dangaard Brouer
2018-04-04 1:16 ` David Ahern
2018-04-04 3:15 ` Md. Islam
2018-04-06 2:55 ` David Ahern
2018-04-10 4:27 ` Md. Islam
2018-04-04 6:16 ` Jesper Dangaard Brouer
2018-04-04 21:09 ` Md. Islam
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=20180402095159.54c48aba@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=agaceph@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=mislam4@kent.edu \
--cc=netdev@vger.kernel.org \
--cc=xemul@openvz.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).