From: Rostislav Lisovy <lisovy@gmail.com>
To: netdev@vger.kernel.org
Cc: linux-can@vger.kernel.org, pisa@cmp.felk.cvut.cz,
sojkam1@fel.cvut.cz, oliver@hartkopp.net,
Rostislav Lisovy <lisovy@gmail.com>
Subject: [PATCH iproute2 0/3] CAN Filter/Classifier
Date: Fri, 25 May 2012 11:11:43 +0200 [thread overview]
Message-ID: <1337937106-7640-1-git-send-email-lisovy@gmail.com> (raw)
The CAN classifier may be used with any available qdisc on Controller
Area Network (CAN) frames passed through AF_CAN networking subsystem.
The classifier classifies CAN frames according to their identifiers.
It can be used on CAN frames with both SFF or EFF identifiers.
The filtering rules for EFF frames are stored in an array, which
is traversed during classification. A bitmap is used to store SFF
rules -- one bit for each ID.
More info about the project:
http://rtime.felk.cvut.cz/can/socketcan-qdisc-final.pdf
Rostislav Lisovy (3):
Added missing can.h
CAN Filter/Classifier -- Source code
CAN Filter/Classifier -- Documentation
include/linux/can.h | 112 ++++++++++++++++++++++
include/linux/pkt_cls.h | 10 ++
man/man8/tc-can.8 | 97 +++++++++++++++++++
tc/Makefile | 1 +
tc/f_can.c | 238 +++++++++++++++++++++++++++++++++++++++++++++++
5 files changed, 458 insertions(+)
create mode 100644 include/linux/can.h
create mode 100644 man/man8/tc-can.8
create mode 100644 tc/f_can.c
--
1.7.9.5
next reply other threads:[~2012-05-25 9:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 9:11 Rostislav Lisovy [this message]
2012-05-25 9:11 ` [PATCH iproute2 1/3] Added missing can.h Rostislav Lisovy
2012-05-25 9:11 ` [PATCH iproute2 2/3] CAN Filter/Classifier -- Source code Rostislav Lisovy
2012-05-25 9:11 ` [PATCH iproute2 3/3] CAN Filter/Classifier -- Documentation Rostislav Lisovy
-- strict thread matches above, loose matches on Subject: below --
2012-06-04 16:09 [PATCH iproute2 0/3] CAN Filter/Classifier Rostislav Lisovy
2012-06-04 19:13 ` Stephen Hemminger
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=1337937106-7640-1-git-send-email-lisovy@gmail.com \
--to=lisovy@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oliver@hartkopp.net \
--cc=pisa@cmp.felk.cvut.cz \
--cc=sojkam1@fel.cvut.cz \
/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).