From: Michal Sojka Date: Mon, 14 May 2012 16:07:23 +0000 (+0200) Subject: man page changes X-Git-Url: https://rtime.felk.cvut.cz/gitweb/lisovros/iproute2_canprio.git/commitdiff_plain/98518515a670d7616a7636b3343b5469feda4441 man page changes --- diff --git a/man/man8/tc-can.8 b/man/man8/tc-can.8 index 891ba33..1ca65be 100644 --- a/man/man8/tc-can.8 +++ b/man/man8/tc-can.8 @@ -38,12 +38,13 @@ are parsed as hexadecimal input. .SH DESCRIPTION The CAN classifier may be used with any available .B qdisc -on Controller Area Network (CAN) frames passed through networking subsystem -via SocketCAN. The classifier operates on CAN frames according to their -identifiers. It can be used on both CAN frames with SFF or EFF identifiers. +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. It is possible to add CAN classifier to any qdisc configured on any networking -device, however it will classify only packets where protocol is set to CAN. +device, however it will ignore non-CAN packets. .SH CLASSIFICATION @@ -56,9 +57,10 @@ increases with the number of configured rules. The filter implements an optimization for matching SFF frames using a bitmap with one bit for every ID. With this optimization, the classification time for SFF frames is nearly constant independently of the number of rules. -Rules for EFF frames are stored in an array. +Rules for EFF frames are always stored in an array. -With very few configured SFF rules, the use of an array may be although faster. +With very few configured SFF rules, the use of an array may be +faster, though. The decision whether to use the bitmap- or array-based implementation needs to be done at compile time.