From: Wojciech Drewek <wojciech.drewek@intel.com>
To: netdev@vger.kernel.org
Cc: dsahern@gmail.com, stephen@networkplumber.org
Subject: [PATCH iproute-next v2 0/3] PPPoE support in tc-flower
Date: Thu, 28 Jul 2022 10:44:34 +0200 [thread overview]
Message-ID: <20220728084437.486187-1-wojciech.drewek@intel.com> (raw)
This patchset implements support for matching
on PPPoE specific fields using tc-flower.
First patch introduces small refactor which allows
to use same mechanism of finding protocol for
both ppp and ether protocols. Second patch
adds support for parsing ppp protocols.
Last patch is about parsing PPPoE fields.
Kernel changes:
https://lore.kernel.org/netdev/20220726203133.2171332-1-anthony.l.nguyen@intel.com/T/#t
Wojciech Drewek (3):
lib: refactor ll_proto functions
lib: Introduce ppp protocols
f_flower: Introduce PPPoE support
include/rt_names.h | 3 ++
include/uapi/linux/pkt_cls.h | 3 ++
include/uapi/linux/ppp_defs.h | 37 ++++++++++++++++++++++
include/utils.h | 10 ++++++
lib/Makefile | 2 +-
lib/ll_proto.c | 33 +++++---------------
lib/ppp_proto.c | 52 +++++++++++++++++++++++++++++++
lib/utils.c | 34 ++++++++++++++++++++
man/man8/tc-flower.8 | 17 +++++++++-
tc/f_flower.c | 58 +++++++++++++++++++++++++++++++++++
10 files changed, 222 insertions(+), 27 deletions(-)
create mode 100644 include/uapi/linux/ppp_defs.h
create mode 100644 lib/ppp_proto.c
--
2.31.1
next reply other threads:[~2022-07-28 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 8:44 Wojciech Drewek [this message]
2022-07-28 8:44 ` [PATCH iproute-next v2 1/3] lib: refactor ll_proto functions Wojciech Drewek
2022-07-28 8:44 ` [PATCH iproute-next v2 2/3] lib: Introduce ppp protocols Wojciech Drewek
2022-07-28 8:44 ` [PATCH iproute-next v2 3/3] f_flower: Introduce PPPoE support Wojciech Drewek
2022-07-28 10:47 ` Guillaume Nault
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=20220728084437.486187-1-wojciech.drewek@intel.com \
--to=wojciech.drewek@intel.com \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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.