All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Pfifo_fast "Unknown qdisc" and asking for basic design
Date: Fri, 11 Nov 2005 14:22:05 +0000	[thread overview]
Message-ID: <4374A90D.6070804@dsl.pipex.com> (raw)
In-Reply-To: <BF782D07436CAE4B931BFA5B2C68FF4F0F8B9E@bmts1.ad.bmtseatech.co.uk>

Mark Lidstone wrote:
> Hi all,
> 
> I've done a search through the archives but I can't find a
> cause/solution to this.
> 
> I'm running a FC4 box with the stock 2.6.12 kernel and a FC2 box with a
> stock 2.6.9 kernel.  I'm obviously using
> iproute2 and the patched tc.
> 
> When I clear down the qdiscs with "tc qdisc del dev <DEV> root" I get
> the following in response to "tc qdisc":
> 
> 	qdisc pfifo_fast 0: dev eth0 [Unknown qdisc, optlen ]
> 	qdisc pfifo_fast 0: dev eth1 [Unknown qdisc, optlen ]
> 
> Unfortunately I cannot add pfifo_fast as a queue type (I was hoping to
> use one - see below).  Have I missed something?

pfifo_fast is what you get as default on interfaces - it's just like 
prio but not meant to be used by you - I suppose you could nest prios, 
but in this case I think what you need is just pfifo or bfifo.


> 
> Secondly, I was wondering if anyone could look over what I am trying to
> do and point out any stupid mistakes I've made.  I am trying to get the
> following setup working:
> 
>               root
>                |
>                |
>               PRIO
>              / | \
>       ______/  |  \______
>      |         |         |
>      0         |         2
>  pfifo_fast    1        sfq
>               HTB__________
>              / | \         \
>       ______/  |  \______   \______
>      |         |         |         |
>     sfq       sfq       sfq       sfq
> 
> Basically, we have 4 companies that will be sharing bandwidth on a
> connection (the four sfq's at the bottom) and some video conferencing
> equipment that needs priority over everything (the pfifo_fast).  Have I
> misunderstood anything vital here?

You would be better off having htb as root so you can throttle traffic 
to below link speed. You can htb's prio parameter to do much the same.

Sfq is nice but the perturb causes packet reordering I would think about 
trying to seperate each customers traffic into bulk and interactive 
aswell and just use sfq on bulk.

Andy.


> 
> Many thanks,
> 
> Mark Lidstone
> IT and Network Support Administrator
> 
> BMT SeaTech Ltd
> Grove House, Meridians Cross, 7 Ocean Way Ocean Village, Southampton.
> SO14 3TJ. UK
> Tel: +44 (0)23 8063 5122         
> Fax: +44 (0)23 8063 5144
> 
> E-Mail:  mailto:mark.lidstone@bmtseatech.co.uk
> Website: www.bmtseatech.co.uk
> ====================================
> =
> Confidentiality Notice and Disclaimer: 
> The contents of this e-mail and any attachments are intended only for
> the use of the e-mail addressee(s) shown. If you are not that person, or
> one of those persons, you are not allowed to take any action based upon
> it or to copy it, forward, distribute or disclose the contents of it and
> you should please delete it from your system. BMT SeaTech Limited does
> not accept liability for any errors or omissions in the context of this
> e-mail or its attachments which arise as a result of Internet
> transmission, nor accept liability for statements which are those of the
> author and not clearly made on behalf of BMT SeaTech Limited.
> ====================================
> =
>   
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
> 

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2005-11-11 14:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-11  9:50 [LARTC] Pfifo_fast "Unknown qdisc" and asking for basic design Mark Lidstone
2005-11-11 14:22 ` Andy Furniss [this message]
2005-11-11 16:29 ` Mark Lidstone
2005-11-14 22:36 ` Andy Furniss
2005-11-15 10:31 ` Mark Lidstone
2005-11-15 18:59 ` Stephen Hemminger
2005-11-16 13:12 ` Mark Lidstone
2005-11-16 14:55 ` 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=4374A90D.6070804@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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.