All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andyqos@ukfsn.org>
To: Andrew Beverley <andy@andybev.com>
Cc: "John A. Sullivan III" <jsullivan@opensourcedevel.com>,
	Lloyd Standish <lloyd@crnatural.net>,
	"netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: prio + policing filter on ingress?
Date: Thu, 15 Dec 2011 20:48:31 +0000	[thread overview]
Message-ID: <4EEA5D1F.6080805@ukfsn.org> (raw)
In-Reply-To: <1323893613.1995.152.camel@andybev-desktop>

Andrew Beverley wrote:

>
> Well according to a question just posted to the (new) LARTC mailing
> list,

Interesting - where's the new list please?


>> HFSC might not be a bad idea for you.  I'm still trying to get my head
>> around it
>
> Ah yes, I've noticed the questions on the netdev list. Thanks for that -
> I just need to spend some time reading through the details now!

That's a lot to digest.

One thing that I recall from when hfsc first came out is that when 
testing it wouldn't limit bulk if the class wasn't backlogged.

For most people if you have enough bandwidth I doubt this is an issue, 
but at the time I was limiting for a 256kit dsl line with five users.

The hfsc paper says (IIRC) that the system will be backlogged until the 
last bit is transmitted - this would have made it really useful for me, 
but the Linux implementation didn't (doesn't?) seem to behave like this, 
so with five empty bulk classes firing five packets at them all would 
instantly dequeue borking my latency 5x more that I could achieve with 
htb classes with low burst set.

Of course htb isn't perfect and will sometime dequeue more than one at a 
time when multiple classes backlogged (hfsc probably wins in this case) 
it's just that one test put me off hfsc. Now I have more bandwidth this 
new documentation could be very useful - thanks for taking the time and 
effort.

I assume it's still "mean" by dropping unclassified traffic if you don't 
set a default class - that used to catch people out as htb was the 
opposite so at least you didn't loose your arp while playing around.

  reply	other threads:[~2011-12-15 20:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12 15:27 prio + policing filter on ingress? Lloyd Standish
2011-12-13 18:25 ` Andrew Beverley
2011-12-13 20:19   ` Lloyd Standish
2011-12-13 21:51     ` Andrew Beverley
2011-12-13 22:53       ` John A. Sullivan III
2011-12-14 20:13         ` Andrew Beverley
2011-12-15 20:48           ` Andy Furniss [this message]
2011-12-15 21:29             ` John A. Sullivan III
2011-12-15 22:08               ` Andy Furniss
2011-12-19  9:53             ` Andrew Beverley
2011-12-19 11:25               ` LARTC mailing list [was: Re: prio + policing filter on ingress?] Niccolò Belli
2011-12-19 17:07                 ` John A. Sullivan III
2011-12-19 17:11                 ` Andrew Beverley
2011-12-19 19:59                   ` LARTC mailing list David Miller
2011-12-19 20:59                     ` Niccolò Belli
2011-12-20 10:45                     ` Andy Furniss

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=4EEA5D1F.6080805@ukfsn.org \
    --to=andyqos@ukfsn.org \
    --cc=andy@andybev.com \
    --cc=jsullivan@opensourcedevel.com \
    --cc=lloyd@crnatural.net \
    --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 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.