From: Jon Zeeff <jzeeff@internet2.edu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multiple connections
Date: Mon, 01 Dec 2003 13:51:09 +0000 [thread overview]
Message-ID: <marc-lartc-107028877225791@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106445243827957@msgid-missing>
sfq generally creates a queue per connection. What you want is a simple
modification to allow per source (for outgoing traffic) ip address allocation.
>>The one downloading with multiple connections gets 90-95% of the bandwidth
>>and the other client gets almost nothing.
>>
> u sure ur using sfq ?
>>
>>And of course, most of the time a client will have multiple connections to
>>the Internet, not only one.
>>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-12-01 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 1:19 [LARTC] Multiple connections carlosh
2003-12-01 8:15 ` Mihai Vlad
2003-12-01 12:03 ` Chijioke Kalu
2003-12-01 13:51 ` Jon Zeeff [this message]
2003-12-02 8:54 ` rio
2003-12-02 9:29 ` raptor
2003-12-02 15:42 ` Mihai Vlad
2003-12-03 10:10 ` Stef Coene
2004-06-10 19:35 ` [LARTC] multiple connections David Magda
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-107028877225791@msgid-missing \
--to=jzeeff@internet2.edu \
--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.