From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Valdis.Kletnieks@vt.edu
Cc: jimis@gmx.net, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Feature proposal (scheduling related)
Date: 23 Jul 2003 15:23:27 +0100 [thread overview]
Message-ID: <1058970206.5520.71.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <200307231417.h6NEHoqj010244@turing-police.cc.vt.edu>
On Mer, 2003-07-23 at 15:17, Valdis.Kletnieks@vt.edu wrote:
> Basically, you're stuck. The biggest part of the problem is that although you
> can certainly control the outbound packets, you have no real control over when
> inbound packets arrive at the other end of your dial-up. One person suggested
> using QoS to help things along - but that needs to be implemented at the OTHER
> end of the dial-up - which means unless your provider does QoS on the terminal
> server, you're basically stuck. Packets will probably just get queued up in
> order of arrival.
There are a few things that help in the general real world but not
mathematical sense. Use an ftp client like gnome-ftp which can set the
rate it accepts data and window sizes. It'll still jam the modem a
little when it starts a transfer but then it'll generally be ok if you
have a bit of buffering for your icecast stream.
next prev parent reply other threads:[~2003-07-23 14:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 10:57 Feature proposal (scheduling related) jimis
2003-07-23 11:24 ` David M. Wilson
2003-07-23 11:43 ` Pavel Machek
2003-07-25 20:24 ` Marcelo Tosatti
2003-07-28 9:29 ` Pavel Machek
2003-07-23 14:17 ` Valdis.Kletnieks
2003-07-23 14:23 ` Alan Cox [this message]
2003-07-23 15:10 ` Richard B. Johnson
2003-07-23 15:13 ` Antonio Vargas
2003-07-23 16:55 ` Disconnect
2003-07-23 17:22 ` David S. Miller
2003-07-23 14:47 ` Greg Stark
2003-07-23 22:17 ` jimis
2003-07-24 0:58 ` Mike Fedyk
2003-07-24 4:04 ` Andre Tomt
[not found] <cpvY.4hH.25@gated-at.bofh.it>
2003-07-23 11:54 ` Ihar "Philips" Filipau
2003-07-23 12:42 Frederick, Fabian
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=1058970206.5520.71.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Valdis.Kletnieks@vt.edu \
--cc=jimis@gmx.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).