All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mr Ivan Hawkes <blackhawk@ivanhawkes.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] boring question
Date: Sun, 25 Apr 2004 13:06:30 +0000	[thread overview]
Message-ID: <408BB7D6.9080608@ivanhawkes.com> (raw)
In-Reply-To: <20040422214238.8E57A44CB@outpost.ds9a.nl>

Andy Furniss wrote:

> Mr Ivan Hawkes wrote:
> 
>> It is important to note that this generally works well for outgoing 
>> traffic but is not particularly effective against incoming traffic 
>> since that is *pushed* onto your machine and it has no way to control 
>> this.
> 
> 
> You can control incoming bandwidth much the same as outbound - but it's 
> hard to keep latency low all of the time.
> 
> Andy.
> 
> 
Are you able to selectively control incoming bandwidth? e.g. I have some 
BT's running sucking up all that good bandwidth and my incoming pipe 
gets saturated (it's 2MB, so this doesn't generally happen). How would I 
tell the BT streams to slow down while giving more priority to the 
important stuff? I know how to do it on egress, just not on ingress.

-- 

http://www.ivanhawkes.com  |  ICQ: 173-392-038

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

  parent reply	other threads:[~2004-04-25 13:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22 18:43 [LARTC] boring question James
2004-04-23 18:08 ` Mr Ivan Hawkes
2004-04-24 23:01 ` Andy Furniss
2004-04-25 13:06 ` Mr Ivan Hawkes [this message]
2004-04-26  7:47 ` Andy Furniss

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=408BB7D6.9080608@ivanhawkes.com \
    --to=blackhawk@ivanhawkes.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.