Re: [dccp] Packet size s on CCID3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 9/22/06, Gorry Fairhurst <gorry@xxxxxxxxxxxxxx> wrote:
Let, me add a few more thoughts, and see what others think...

* I also have a problem with how to find "s" when thinking about an
"unknown" application. I'm not really sure how this is intended to work for
variable-sized packets. Calculating an average value for an application that
naturally varies the size doesn't seem to me to be straight-forward.

One value of "s" that makes sense, is possibly the largest segment size sent
by the session. This is at least conservative - for fixed-sized flows it is
identical to the optimum "s". For bursty flows, it is safe.

It is actually the opposite of what you say here. If you do the maths
and set s large then you can send more packets per second than what
you should be able to.

--
Ian McDonald
Web: http://wand.net.nz/~iam4
Blog: http://imcdnzl.blogspot.com
WAND Network Research Group
Department of Computer Science
University of Waikato
New Zealand
-
To unsubscribe from this list: send the line "unsubscribe dccp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [IETF DCCP]     [Linux Networking]     [Git]     [Security]     [Linux Assembly]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]

  Powered by Linux