From: Jesper Dangaard Brouer <hawk@diku.dk>
To: Netfilter Developers <netfilter-devel@vger.kernel.org>
Cc: paulmck@linux.vnet.ibm.com, Eric Dumazet <eric.dumazet@gmail.com>,
netdev <netdev@vger.kernel.org>
Subject: [RFC 0/3] MPEG2/TS drop analyzer iptables match extension
Date: Tue, 19 Oct 2010 16:21:33 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.1010191608080.18708@ask.diku.dk> (raw)
This is my iptables match module for analyzing IPTV MPEG2/TS streams.
Currently it only detects dropped packets, but I want to extend it for
analyzing jitter and bursts.
Jan Engelhardt convinced me that I should just send the module as-is
for review on the list. I wrote the code in 2009, and have only done
some minor changes to make it work on kernel 2.6.35 since.
The code is running in our production environment, where it handles
approx 120 TV-channels which gives an approx 600 Mbit/s bandwidth
usage. The production hardware are using an ATOM 330 CPU (1.6Ghz),
and a PCI-express attached NIC Intel 82576 (driver igb).
I take advantage of the multiqueue features in the 82576 Intel NIC.
This together with using RCU locking, makes the module scale very well
to several CPUs (the ATOM 330 has two cores with HyperTreading).
The total CPU load on production is only 10% CPU load (6-7% in softirq).
I do "deep-packet-inspection" of the IP packet in order to process the
7 internal TS (Transport Stream) packets.
I have placed the presentation I'm giving at Netfilter Workshop 2010 on
the Wiki list of presentations:
http://workshop.netfilter.org/2010/wiki/index.php/List_of_presentations
and a direct link here:
http://workshop.netfilter.org/2010/presentations/IPTV-burst-issues-NFWS2010-JesperBrouer.odp
Cheers,
Jesper Brouer
--
-------------------------------------------------------------------
MSc. Master of Computer Science
Dept. of Computer Science, University of Copenhagen
Author of http://www.adsl-optimizer.dk
-------------------------------------------------------------------
next reply other threads:[~2010-10-19 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 14:21 Jesper Dangaard Brouer [this message]
2010-10-19 14:25 ` [RFC 1/3] MPEG2/TS drop analyzer file: xt_mp2t.h Jesper Dangaard Brouer
2010-10-19 14:26 ` [RFC 2/3] MPEG2/TS drop analyzer file: xt_mp2t.c Jesper Dangaard Brouer
2010-10-19 14:27 ` [RFC 3/3] MPEG2/TS drop analyzer file: libxt_mp2t.c Jesper Dangaard Brouer
2010-11-04 0:16 ` [RFC 0/3] MPEG2/TS drop analyzer iptables match extension Jan Engelhardt
2010-11-04 9:20 ` Jesper Dangaard Brouer
2010-11-04 10:29 ` Jan Engelhardt
2010-11-10 11:02 ` Jesper Dangaard Brouer
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=Pine.LNX.4.64.1010191608080.18708@ask.diku.dk \
--to=hawk@diku.dk \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
/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