From: Carmine Scarpitta <carmine.scarpitta@uniroma2.it>
To: davem@davemloft.net
Cc: kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org, kuba@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
ahmed.abdelsalam@gssi.it, david.lebrun@uclouvain.be,
dav.lebrun@gmail.com, andrea.mayer@uniroma2.it,
paolo.lungaroni@cnit.it,
Carmine Scarpitta <carmine.scarpitta@uniroma2.it>
Subject: [net-next 0/2] Add support for SRv6 End.DT4 action
Date: Thu, 13 Feb 2020 02:09:30 +0100 [thread overview]
Message-ID: <20200213010932.11817-1-carmine.scarpitta@uniroma2.it> (raw)
Hi,
this patch series adds the support for SRv6 End.DT4 action.
End.DT4 decapsulates the received packets and does IPv4 routing
lookup in a specific routing table.
The IPv4 routing subsystem does not allow to specify the routing
table in which the lookup has to be performed.
Patch 1 enables to perform IPv4 FIB lookup in a predefined FIB table.
Patch 2 adds the support for SRv6 End.DT4 action.
Thanks,
Carmine Scarpitta
Carmine Scarpitta (2):
Perform IPv4 FIB lookup in a predefined FIB table
Add support for SRv6 End.DT4 action
include/net/route.h | 2 +-
net/ipv4/route.c | 22 ++++++++++++-------
net/ipv6/seg6_local.c | 49 +++++++++++++++++++++++++++++++++++++++++++
3 files changed, 64 insertions(+), 9 deletions(-)
--
2.17.1
next reply other threads:[~2020-02-13 1:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 1:09 Carmine Scarpitta [this message]
2020-02-13 1:09 ` [net-next 1/2] Perform IPv4 FIB lookup in a predefined FIB table Carmine Scarpitta
2020-02-15 18:06 ` David Ahern
2020-02-18 23:50 ` Carmine Scarpitta
2020-02-19 1:05 ` David Ahern
2020-02-19 2:49 ` Carmine Scarpitta
2020-02-19 4:29 ` David Ahern
2020-02-20 22:33 ` Carmine Scarpitta
2020-02-21 17:31 ` David Ahern
2020-03-06 16:45 ` Ahmed Abdelsalam
2020-03-09 15:36 ` David Ahern
2020-03-10 16:26 ` Ahmed Abdelsalam
2020-02-13 1:09 ` [net-next 2/2] Add support for SRv6 End.DT4 action Carmine Scarpitta
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=20200213010932.11817-1-carmine.scarpitta@uniroma2.it \
--to=carmine.scarpitta@uniroma2.it \
--cc=ahmed.abdelsalam@gssi.it \
--cc=andrea.mayer@uniroma2.it \
--cc=dav.lebrun@gmail.com \
--cc=davem@davemloft.net \
--cc=david.lebrun@uclouvain.be \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paolo.lungaroni@cnit.it \
--cc=yoshfuji@linux-ipv6.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).