All of lore.kernel.org
 help / color / mirror / Atom feed
From: Victor Cassar <victorcassar@yahoo.com>
To: lartc@vger.kernel.org
Subject: Re: [Fwd: [LARTC] quantum value for voip]
Date: Mon, 17 Feb 2003 15:32:59 +0000	[thread overview]
Message-ID: <marc-lartc-104549608024818@msgid-missing> (raw)

Tnx Mathieu

I will try with pfifo, my voice traffic can be marked
with diffserv from the source device, so i´ll try to
take advantage of this marked traffic

regards


--- Mathieu Deziel <mathieu.deziel@crc.ca> wrote:
> Hi Victor,  see below.
> 
> >
> > >Why not a simple fifo?  You can adapt the size of
> it
> > >from the command line.
> 
> > I want tu use this pfifo queue i know its
> hardwired
> > and that i need to mark packets here or from the
> > source
> > in order to use dscp field
> >
> 
> The pfifo and bfifo qdiscs are not "hardwired". 
> Their size is configurable (specified in bytes for
> the bfifo, and in number of packets for the pfifo). 
> The one that is hardwired is the pfifo_fast:  it is
> the default qdisc, the one that is there when you
> don't configure anything.  The pfifo_fast has 3
> internal prio
> queues.  Packets are classified in one of the three
> prio queue according to the dscp mark, just like you
> said in you previous mail.  Yes, to make use of the
> priority capability of pfifo_fast, your packets must
> marked before they enter the tc software.  You can
> use iptables to mark the packets before they enter
> tc.
> 
> Another thing you can do it make use of the prio
> qdisc, and then create your own (u32) filters.  You
> can then mark the packets with dsmark before the
> packets go out, if you want.
> 
> Hope this helps,
> Mathieu.
> 


__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

                 reply	other threads:[~2003-02-17 15:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-104549608024818@msgid-missing \
    --to=victorcassar@yahoo.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.