From: Robert Hancock <hancockr@shaw.ca>
To: Lukas Hejtmanek <xhejtman@mail.muni.cz>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>
Subject: Re: UDP packets scheduling
Date: Tue, 20 Mar 2007 17:55:31 -0600 [thread overview]
Message-ID: <46007473.7070001@shaw.ca> (raw)
In-Reply-To: <fa.Mj0BY4rypcd66zFbzfAQxZCpUVk@ifi.uio.no>
Lukas Hejtmanek wrote:
> On Tue, Mar 20, 2007 at 06:52:51PM +0100, Andi Kleen wrote:
>>> Flow control must be turned off for some other reason.
>> That's your fundamental problem. Fix that.
>>
>> Even if you get the rate right there can be many reasons why timing
>> gets disrupted temporarily and to recover from any of this you need
>> working flow control.
>
> How do you want to enable wire/fibre flow control, e.g., from Europe to USA?
> You are not guaranteed any hardware based flow control.
>
> And as of software flow control, you need precise timing of UDP packets to
> keep desired packet rate. How to do it at speeds about 5.5Gbps, that is my
> question.
Why is it necessary to avoid bursting? There should be enough buffering
along the chain to avoid packet loss with reasonable burst sizes.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-03-20 23:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.CWur1AzeHpCwg8xikmKYIrHD+vg@ifi.uio.no>
[not found] ` <fa.XuXSOUdBq9+oYcuagtcjLic4XjE@ifi.uio.no>
[not found] ` <fa.Mj0BY4rypcd66zFbzfAQxZCpUVk@ifi.uio.no>
2007-03-20 23:55 ` Robert Hancock [this message]
2007-03-20 0:52 UDP packets scheduling Lukas Hejtmanek
2007-03-20 2:37 ` David Schwartz
2007-03-20 16:31 ` Stephen Hemminger
2007-03-20 16:42 ` Jan Engelhardt
2007-03-20 17:52 ` Andi Kleen
2007-03-20 17:21 ` Lukas Hejtmanek
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=46007473.7070001@shaw.ca \
--to=hancockr@shaw.ca \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xhejtman@mail.muni.cz \
/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