From: Michal Soltys <soltys@ziu.info>
To: Julien Vehent <julien@linuxwall.info>
Cc: netfilter <netfilter@vger.kernel.org>
Subject: Re: SFQ hash question
Date: Sun, 13 Sep 2009 00:12:09 +0200 [thread overview]
Message-ID: <4AAC1CB9.40806@ziu.info> (raw)
In-Reply-To: <ae7bd0d6efc754477dbee35dedeaf6db@localhost>
Julien Vehent wrote:
>
> One theoritical question: imagine I would like to give a hand on the man
> pages, who should I contact?
>
Well, the maintainer of respective utility/ies + proper devel mailing list.
Note, that tc, ip, ss - things related to iproute2 in general - belong to netdev,
not netfilter-devel. Similary user questions about iproute2 -> net, not netfilter.
AFAIK. Don't remove CC entries either.
As for docs in general, be sure to peek over:
http://www.linuxfoundation.org/en/Net
http://ace-host.stuart.id.au/russell/files/tc/doc/
http://b42.cz/notes/u32_classifier/
http://www.stearns.org/doc/iptables-u32.v0.1.7.html (note that negative offsets don't work though)
http://jengelh.medozas.de/images/nf-packet-flow.png
http://marc.info/?l=lartc&m=117569441229800&w=2 (basic matches)
http://marc.info/?l=linux-netdev&m=120180241422360&w=2 (external hashing, for sfq mainly)
doc subdirectory of iproute2
Documentation[/networking] subdirectory of kernel tree
book: "Understanding Linux Network Internals"
http://www.policyrouting.org/PolicyRoutingBook/ONLINE/TOC.html
http://www.cs.cmu.edu/~istoica/hfsc-tr.ps.gz
( depending on gs version, you might need: sed "s|\[FontBBox\]|/FontBBox load |" )
http://www.sonycsl.co.jp/~kjc/software/TIPS.txt (*BSD oriented, still interesting tidbits)
Some of the above will feel pretty heavy.
prev parent reply other threads:[~2009-09-12 22:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 13:50 SFQ hash question Julien Vehent
2009-09-11 15:03 ` Julien Vehent
2009-09-11 15:12 ` Michal Soltys
[not found] ` <2643b2d5a75307da3d00e97e0245bcf9@localhost>
[not found] ` <4AAA70A4.8030707@ziu.info>
2009-09-11 15:53 ` Julien Vehent
2009-09-12 22:12 ` Michal Soltys [this message]
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=4AAC1CB9.40806@ziu.info \
--to=soltys@ziu.info \
--cc=julien@linuxwall.info \
--cc=netfilter@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox