All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vik Heyndrickx" <vik.heyndrickx@pandora.be>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Basic Qdisc : PRIO, pfifo_fast
Date: Mon, 07 Jan 2002 20:31:30 +0000	[thread overview]
Message-ID: <marc-lartc-101043553519799@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101040301100359@msgid-missing>

> -----Original Message-----
> From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]On
> Behalf Of bert hubert
> Sent: Monday, January 07, 2002 5:37 PM
> To: Francesco Schiavello
> Cc: lartc@mailman.ds9a.nl
> Subject: Re: [LARTC] Basic Qdisc : PRIO, pfifo_fast
>
> On Mon, Jan 07, 2002 at 12:29:18PM +0100, Francesco Schiavello wrote:
>
> > Yet I cannot find any examples concerning these Qdisc (for pfifo_fast I
> > cannot even find manpages) .
>
> pfifo_fast:
> http://ds9a.nl/lartc/HOWTO//cvs/2.4routing/output/2.4routing-9.html#ss9.2

> You can't really configure a lot about pfifo_fast - it is the default.

Howdy, I've just happily subscribed to lartc.

It may be worthwhile to add to FAQ that if you have a cbq or some other
queuing discipline attached to the network device, and you want to go back
to pfifo_fast qdisc, you can achieve this by simply deleting the current
qdisc. Then pfifo_fast falls just in place.
I don't know whether this is the right way, but it works for me, and since
it is linux, this makes it the right way ;-)

Kind regards,

--
Vik


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

  parent reply	other threads:[~2002-01-07 20:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-07 11:29 [LARTC] Basic Qdisc : PRIO, pfifo_fast Francesco Schiavello
2002-01-07 16:36 ` bert hubert
2002-01-07 20:31 ` Vik Heyndrickx [this message]
2002-01-07 21:32 ` bert hubert

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-101043553519799@msgid-missing \
    --to=vik.heyndrickx@pandora.be \
    --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.