Go to file
John Hurley f5c977eed7 nfp: flower: detect potential pre-tunnel rules
Pre-tunnel rules are used when the tunnel end-point is on an 'internal
port'. These rules are used to direct the tunnelled packets (based on outer
header fields) to the internal port where they can be detunnelled. The
rule must send the packet to ingress the internal port at the TC layer.

Currently FW does not support an action to send to ingress so cannot
offload such rules. However, in preparation for populating the pre-tunnel
table to represent such rules, check for rules that send to the ingress of
an internal port and mark them as such. Further validation of such rules
is left to subsequent patches.

Signed-off-by: John Hurley <john.hurley@netronome.com>
Reviewed-by: Simon Horman <simon.horman@netronome.com>
Acked-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2019-08-06 14:24:21 -07:00
arch arm64: dts: fsl: ls1028a: Enable eth port1 on the ls1028a QDS board 2019-08-02 18:22:18 -07:00
block
certs
crypto
Documentation dt-bindings: net: fsl: enetc: Add bindings for the central MDIO PCIe endpoint 2019-08-02 18:22:18 -07:00
drivers nfp: flower: detect potential pre-tunnel rules 2019-08-06 14:24:21 -07:00
fs for-5.3-rc1-tag 2019-07-22 09:08:38 -07:00
include net: sched: add ingress mirred action to hardware IR 2019-08-06 14:24:21 -07:00
init
ipc
kernel Merge branch 'sched-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip 2019-07-22 09:30:34 -07:00
lib
LICENSES
mm
net net: sched: add ingress mirred action to hardware IR 2019-08-06 14:24:21 -07:00
samples
scripts
security
sound
tools ][next] selftests: nettest: fix spelling mistake: "potocol" -> "protocol" 2019-08-05 10:27:53 -07:00
usr
virt
.clang-format
.cocciconfig
.get_maintainer.ignore
.gitattributes
.gitignore
.mailmap
COPYING
CREDITS
Kbuild
Kconfig
MAINTAINERS NFC: nxp-nci: Get rid of platform data 2019-07-29 08:56:26 -07:00
Makefile Linus 5.3-rc1 2019-07-21 14:05:38 -07:00
README

Linux kernel
============

There are several guides for kernel developers and users. These guides can
be rendered in a number of formats, like HTML and PDF. Please read
Documentation/admin-guide/README.rst first.

In order to build the documentation, use ``make htmldocs`` or
``make pdfdocs``.  The formatted documentation can also be read online at:

    https://www.kernel.org/doc/html/latest/

There are various text files in the Documentation/ subdirectory,
several of them using the Restructured Text markup notation.

Please read the Documentation/process/changes.rst file, as it contains the
requirements for building and running the kernel, and information about
the problems which may result by upgrading your kernel.