All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Games and QOS on share connection line
Date: Tue, 12 Apr 2005 16:52:45 +0000	[thread overview]
Message-ID: <425BFCDD.8070802@dsl.pipex.com> (raw)
In-Reply-To: <S2688964AbVDFQhA/20050406163705Z+55196@mail6.centrum.cz>

Ludek Horak wrote:
>>Ludek Horak wrote:
>>
>>
>>>What do you think about this configuration? Do you know better setting for gaming traffic on share connection line? I'd like to know your opinions. I'm appreciating your comments.
>>
>>I wouldn't send interactive type traffic to sfq - perturb causes packet 
>>reordering, it's meant for bulk traffic really.
>>
>>Are the 2/2 and 4/4 internet link - you are OK for bandwidth on wireless?
>>
>>Andy.
> 
> 
> Would you be more specific? I understand that sfq is not the best. Should I create interactive class with pfifo queue discipline 

I would - in a way it doesn't matter that much as you should hope to 
have rates high enough so that interactive doesn't queue anyway.

>and what about parent class? Leave it sfq?

Bulk traffic classes are OK for sfq - parent class doesn't have qdisc 
only leafs.

> Our bandwith is fine and 2/2 is guaranteed internet link.

OK - do you shape incoming aswell.

Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2005-04-12 16:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06 16:37 [LARTC] Games and QOS on share connection line Ludek Horak
2005-04-06 21:50 ` Corey Hickey
2005-04-09 20:20 ` Andy Furniss
2005-04-11 22:46 ` Ludek Horak
2005-04-12 16:52 ` Andy Furniss [this message]

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=425BFCDD.8070802@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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.