All of lore.kernel.org
 help / color / mirror / Atom feed
From: Don Cohen don-lartc@isis.compsvcs.com
To: lartc@vger.kernel.org
Subject: [LARTC] SFQ clarification
Date: Sat, 10 Feb 2001 01:38:18 +0000	[thread overview]
Message-ID: <marc-lartc-98373940416997@msgid-missing> (raw)

<PRE><A HREF="http://www.linuxdoc.org/HOWTO/Adv-Routing-HOWTO.html">http://www.linuxdoc.org/HOWTO/Adv-Routing-HOWTO.html</A>
9.2 Stochastic Fairness Queueing 
says:
 SFQ however cannot determine interactive flows from bulk ones -- one
 usually needs to do the selection with CBQ before, and then direct the
 bulk traffic into SFQ.  

I don't understand this.  You want to give preference to the non-bulk
traffic, right?  And this is what you get if you just put it all into
the same SFQ, right?  All the small flows get fast service and the 
large flows fairly share what's left.  That seems like what you want.
So it's true that SFQ does not distinguish bulk from interactive flows
but there's no need to.


</PRE>

             reply	other threads:[~2001-02-10  1:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-10  1:38 Don [this message]
2001-02-10  4:04 ` [LARTC] SFQ clarification Gregory
2001-02-10  5:14 ` Don

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-98373940416997@msgid-missing \
    --to=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.