From: Daniele Lacamera <root@danielinux.net>
To: "Ian McDonald" <ian.mcdonald@jandi.co.nz>
Cc: 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: Wed, 13 Sep 2006 10:18:39 +0200 [thread overview]
Message-ID: <200609131018.40023.root@danielinux.net> (raw)
In-Reply-To: <5640c7e00609121426t75f5519at562a85f40b64163@mail.gmail.com>
On Tuesday 12 September 2006 23:26, Ian McDonald wrote:
> Where is the published research? If you are going to mention research
> you need URLs to papers and please put this in source code too so
> people can check.
I added the main reference to the code. I am going to give you all the
pointers on this research, mainly recent congestion control proposals
that include pacing.
> I agree with Arnaldo's comments and also would add I don't like having
> to select 1000 as HZ unit. Something is wrong if you need this as I
> can run higher resolution timers without having to do this....
I removed that select in Kconfig, I agree it doesn't make sense at all,
for portability. However, pacing works with 1ms resolution, so maybe
a "depends HZ_1000" is still required. (How do you run 1ms timers with
HZ!=1000?)
Thanks
--
Daniele Lacamera
root@danielinux.net
next prev parent reply other threads:[~2006-09-13 8:18 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 [this message]
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
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=200609131018.40023.root@danielinux.net \
--to=root@danielinux.net \
--cc=ccaini@deis.unibo.it \
--cc=gpau@cs.ucla.edu \
--cc=ian.mcdonald@jandi.co.nz \
--cc=netdev@vger.kernel.org \
--cc=rfirrincieli@arces.unibo.it \
/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).