From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] bfifo/pfifo
Date: Mon, 03 Dec 2001 01:45:10 +0000 [thread overview]
Message-ID: <marc-lartc-100734383704047@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100732995100928@msgid-missing>
On Sun, Dec 02, 2001 at 10:54:25PM +0100, Lutz Pressler wrote:
> Hello,
>
> section 15.1 of 2.4routing-howto talks about bfifo and pfifo qdiscs.
> Do they work?
>
> # ip l l
> ...
> 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
> ...
>
> # tc qdisc add dev eth0 bfifo
> RTNETLINK answers: Invalid argument
tc qdisc add dev eh0 root bfifo ?
> What do I miss? Kernel (2.2.19) has every NET_SCH_ option activated
> (module).
I'm not sure if 2.2 has bfifo/pfifo. 2.4 has.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
Trilab The Technology People
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-12-03 1:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-02 21:54 [LARTC] bfifo/pfifo Lutz Pressler
2001-12-03 1:45 ` bert hubert [this message]
2001-12-03 7:35 ` Lutz Pressler
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=marc-lartc-100734383704047@msgid-missing \
--to=ahu@ds9a.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox