From: Stephen Hemminger <shemminger@osdl.org>
To: root@danielinux.net
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Carlo Caini <ccaini@deis.unibo.it>,
Rosario Firrincieli <rfirrincieli@arces.unibo.it>,
Giovanni Pau <gpau@cs.ucla.edu>
Subject: Re: TCP Pacing
Date: Thu, 14 Sep 2006 10:21:55 +0900 [thread overview]
Message-ID: <20060914102155.3a6552db@localhost.localdomain> (raw)
In-Reply-To: <200609131018.33231.root@danielinux.net>
On Wed, 13 Sep 2006 10:18:31 +0200
Daniele Lacamera <root@danielinux.net> wrote:
> On Wednesday 13 September 2006 05:41, Stephen Hemminger wrote:
> > Pacing in itself isn't a bad idea, but:
> <cut>
> > * Since it is most useful over long delay links, maybe it should be a
> route parameter.
>
Look into rtnetlink and how we keep track of route metrics, and
add a new per route state variable. Need to update iproute2 (ip command)
as well.
> What does this mean? Should I move the sysctl switch elsewhere?
>
> A new (cleaner) patch follows.
> Thanks to you all for your attention & advices.
>
> Signed-off by: Daniele Lacamera <root@danielinux.net>
You may also want into look into high resolution timer (hrtimer),
the resolution doesn't get finer than HZ without using -rt patches.
But the ktime interface is cleaner than the normal timer math.
prev parent reply other threads:[~2006-09-14 1:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 17:58 TCP Pacing Daniele Lacamera
2006-09-12 18:21 ` Arnaldo Carvalho de Melo
2006-09-12 21:26 ` Ian McDonald
2006-09-13 8:18 ` Daniele Lacamera
2006-09-13 15:46 ` Daniele Lacamera
2006-09-16 0:41 ` Xiaoliang (David) Wei
2006-09-19 11:31 ` Daniele Lacamera
2006-09-13 18:30 ` Ian McDonald
2006-09-13 3:41 ` Stephen Hemminger
2006-09-13 8:18 ` Daniele Lacamera
2006-09-14 1:21 ` Stephen Hemminger [this message]
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=20060914102155.3a6552db@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=ccaini@deis.unibo.it \
--cc=davem@davemloft.net \
--cc=gpau@cs.ucla.edu \
--cc=netdev@vger.kernel.org \
--cc=rfirrincieli@arces.unibo.it \
--cc=root@danielinux.net \
/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.