From: Matevz Langus <matevy@arhitektova-delavnica.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Efficient handling of RTP frames?
Date: Tue, 11 May 2004 10:28:02 +0200 [thread overview]
Message-ID: <1084264082.4338.2.camel@n1020> (raw)
In-Reply-To: <20040510205808.GA4313@mars.ravnborg.org>
Hi,
I did the following in advance to all others said before:
left UDP CRC field empty, so you don't need to calculated CRC. VoIP
systems do not complain about that.
rgds,
Matevz
On Mon, 2004-05-10 at 22:58, Sam Ravnborg wrote:
> Hi all.
>
> We (my company) are looking into a solution for transporting a high amount
> of RTP packets across a single CPU. A 82xx, presumeably a 8270.
> With high amount of RTP packets we are talking about 10 to 20.000 packets
> per second with a payload size of ~64 bytes each (on top of UDP header).
>
> The RTP packets needs to be sent between an external device connected
> to one of the FCC's (needs to write our own driver here) and the Ethernet
> port sitting on FCC1.
>
> Does this sound like a dead-end doing this in Linux?
>
> Can anyone point in a direction where to find more information
> about how to realise this in the most efficiet way?
>
> Google did not bring up anything useful.
>
> Thanks in advance,
>
> Sam
>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-11 8:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 20:58 Efficient handling of RTP frames? Sam Ravnborg
2004-05-10 21:16 ` Dan Malek
2004-05-10 21:33 ` Sam Ravnborg
2004-05-11 1:55 ` Dan Malek
2004-05-10 22:22 ` Eugene Surovegin
2004-05-11 8:28 ` Matevz Langus [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-11 21:42 sam
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=1084264082.4338.2.camel@n1020 \
--to=matevy@arhitektova-delavnica.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).