All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Pfifo_fast "Unknown qdisc" and asking for basic design
Date: Tue, 15 Nov 2005 18:59:50 +0000	[thread overview]
Message-ID: <20051115105950.459ed1ed@localhost.localdomain> (raw)
In-Reply-To: <BF782D07436CAE4B931BFA5B2C68FF4F0F8B9E@bmts1.ad.bmtseatech.co.uk>

On Fri, 11 Nov 2005 09:50:03 -0000
"Mark Lidstone" <mark.lidstone@bmtseatech.co.uk> 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 ]
> 

Current versions of iproute2 know about pfifo_fast.

> 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 only suitable as a baseline with no other qdisc's
involved. It can only sit directly on the device (at the bottom).
It shouldn't be that much faster than doing it with prio and fifo for
most things. The additional overhead of prio and fifo are mostly because
they are in separate modules and that adds some memory locality penalty.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-11-15 18:59 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
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 [this message]
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=20051115105950.459ed1ed@localhost.localdomain \
    --to=shemminger@osdl.org \
    --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.