From: jimis@gmx.net
To: linux-kernel@vger.kernel.org
Subject: Re: Feature proposal (scheduling related)
Date: Thu, 24 Jul 2003 01:17:57 +0300 [thread overview]
Message-ID: <3F1F0995.4020300@gmx.net> (raw)
In-Reply-To: <200307231417.h6NEHoqj010244@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
> On Wed, 23 Jul 2003 13:57:41 +0300, jimis@gmx.net said:
>
>>1)I 'm connected to the internet via dial-up, therefore I only have 40 kbits of
>>bandwidth available. What I want to do is listen to icecast radio via xmms (at
>>22 kbits), download the kernel sources with wget, and browse the web at the same
>>time. Currently I think that this is *impossible* (correct me if I'm wrong) as
>>the radio will be full of pauses and the browsing experience painfully slow.
>
>
> 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
But the incoming packets are those that I request to be sent to me (most times).
When I know the packet size I will accept I may not request all packets now, but
a bit later, to leave bandwidth for other requested packets of higher priority.
> 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.
This is what I don't like, but I bet there must be a way to slow down the other
end, even if it has not QoS.
What might help, and needs only be implemented on my side of the connection, is
requesting the packets of higher priorities first. And if I know my total
bandwidth, perhaps I can request as many packets needed to fill it (and not
flood it like it happens now).
Thank you all for your attention,
Dimitris
next prev parent reply other threads:[~2003-07-23 22:00 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
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 [this message]
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=3F1F0995.4020300@gmx.net \
--to=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).