From: Disconnect <lkml@sigkill.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Feature proposal (scheduling related)
Date: 23 Jul 2003 12:55:35 -0400 [thread overview]
Message-ID: <1058979335.1192.78.camel@slappy> (raw)
In-Reply-To: <20030723151321.GC29384@wind.cocodriloo.com>
Alternately, openbsd can do a similar thing with great results (although
I haven't tried it over serial/pppd.) And it works reasonably well even
when done on only one end.
http://www.benzedrine.cx/ackpri.html
On Wed, 2003-07-23 at 11:13, Antonio Vargas wrote:
> You need QoS at the router level to resolve this. Since you are
> running your own routers to connect your ethernet segments, QoS
> should be done at both ends of the connection. If it's available
> on your distro, try wondershaper, it's a nice script which you tell
> your upstream and downstream rates and then it adjusts QoS parameters
> to provide great response. The most important thing is that it prioritises
> ACK packets above everything else. This helps a lot when there is heavy
> traffic (FTP for example) in both directions at the same time.
--
Disconnect <lkml@sigkill.net>
next prev parent reply other threads:[~2003-07-23 16:47 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 [this message]
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=1058979335.1192.78.camel@slappy \
--to=lkml@sigkill.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 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.