From: Lukas Hejtmanek <xhejtman@mail.muni.cz>
To: David Schwartz <davids@webmaster.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Re: ex-upload
Date: Tue, 20 Mar 2007 10:38:34 +0100 [thread overview]
Message-ID: <20070320093834.GO22880@mail.muni.cz> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKCEEACGAC.davids@webmaster.com>
Hello,
>> How can I put delay between subsequent msg sends to achieve desired
>> packet rate without loses, e.g., 3.5Gbps without bursts? Even nanosleep()
>> with the lowest possible delay seems to be too much delay. Busy loop with
>> clock_gettime(3) works OK on SMP boxes, but on UP it causes problems.
>
> Why do you want to avoid bursts? You're going to be bursting between 10Gb/s
> and 0 anyway.
It is because bursts above 5.5Gbps cannot be received by the peer. The peer is
only able to receive bursts up to 5.5Gbps whereas the sender is able to burst
up to 9.9Gbps.
> It sounds like you're deliberately putting impossible requirements on
> yourself choosing the worst possible protocol and demanding the pacing be
> perfect. I don't think the technology to do that is here yet, but why would
> you possibly need it?
it is video transmission encapsulated in RTP over UDP. I do not know whether
there are any other possibilities that would work also on Mac OS or FreeBSD.
(Please Cc me)
--
Lukáš Hejtmánek
next prev parent reply other threads:[~2007-03-20 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 0:52 UDP packets scheduling Lukas Hejtmanek
2007-03-20 2:37 ` David Schwartz
2007-03-20 9:38 ` Lukas Hejtmanek [this message]
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
[not found] <20070318015323.GH12382@kraken.fi.muni.cz>
[not found] ` <20070319135100.GH22880@mail.muni.cz>
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=20070320093834.GO22880@mail.muni.cz \
--to=xhejtman@mail.muni.cz \
--cc=davids@webmaster.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox