All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Turcu <adrian.turcu@gmvinteractive.com>
To: lartc@vger.kernel.org
Subject: [LARTC] MARK vs CLASSIFY with tc
Date: Wed, 06 Apr 2005 15:28:30 +0000	[thread overview]
Message-ID: <200504061628.35365.adrian.turcu@gmvinteractive.com> (raw)

Hello list,

I just wonder if someone did any performance tests (speed of processing the 
packets) or maybe could advise about this two scenario:

1. packets are marked with iptables and processed by tc using filters
2. packets are sent by iptables directly to tc using CLASSIFY chain, thus 
avoiding the tc filters

I had some thinking about these two ways of dealing with egress traffic and my 
logic says that the second should be faster to process the packets, but I 
might be wrong (I guess that being an iproute list there will be a lot of 
people in favour of the first - going even further by skipping iptables all 
together and using detailed filtering with tc).

This came up not just for fun nor that I saw some noticeable differences (not 
with the volume of traffic I'm having at the moment). I want to regulate the 
traffic from a multimedia server (RTSP) and everybody knows that audio/video 
traffic is very sensitive to variable latency and jitter with terrible 
end-user experience.

BTW I'm using HTB with SFQ, kernel 2.6.11.6, iproute2 ss050318 and iptables 
1.3.1. I used PFIFO before SFQ, but it seems that it takes quite a lot for 
the per stream bandwidth to be re-adjusted in case a new session opens and 
I'm already at the limit with the allocated slice from the total available 
pipe.

Thanks for taking your time thinking about this,
Adrian
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2005-04-06 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06 15:28 Adrian Turcu [this message]
2005-04-06 16:18 ` [LARTC] MARK vs CLASSIFY with tc Wang Jian
2005-04-06 16:54 ` Adrian Turcu

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=200504061628.35365.adrian.turcu@gmvinteractive.com \
    --to=adrian.turcu@gmvinteractive.com \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.