[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190530164246.17955-1-ldir@darbyshire-bryant.me.uk>
Date: Thu, 30 May 2019 16:43:15 +0000
From: Kevin 'ldir' Darbyshire-Bryant <ldir@...byshire-bryant.me.uk>
To: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"stephen@...workplumber.org" <stephen@...workplumber.org>
CC: Kevin 'ldir' Darbyshire-Bryant <ldir@...byshire-bryant.me.uk>
Subject: [RFC PATCH iproute2-next 0/1] tc: add support for act ctinfo
Still high on the goods of act_ctinfo being accepted into kernel
net-next I thought it would be a good idea to offer the user space tc
side of things to control the wee beastie.
It's a pretty shameless copy/shunt/paste/hack of m_connmark and some of
the other tc action control programs and does fundamentally work (used
for testing of the kernel module)
There are no doubt some sharp edges that I'd like to knock the corners
off before a realistic attempt at submitting, so this is a general RFC
call to see what I've fundamentally done wrong and can clean up.
eg. I do update uapi/linux/pkt_cls.h to match the relevant bits of what
has gone upstream for act_ctinfo. Should this be a separate commit?
Kevin Darbyshire-Bryant (1):
tc: add support for act ctinfo
include/uapi/linux/pkt_cls.h | 3 +-
include/uapi/linux/tc_act/tc_ctinfo.h | 34 ++++
tc/Makefile | 1 +
tc/m_ctinfo.c | 244 ++++++++++++++++++++++++++
4 files changed, 281 insertions(+), 1 deletion(-)
create mode 100644 include/uapi/linux/tc_act/tc_ctinfo.h
create mode 100644 tc/m_ctinfo.c
--
2.20.1 (Apple Git-117)
Powered by blists - more mailing lists