From: <aacquaviva@deis.unibo.it>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] udp problem & network stack questions
Date: Tue, 11 Jun 2002 17:13:00 -0000 [thread overview]
Message-ID: <200206120011.CAA15114@promet2.deis.unibo.it> (raw)
Hi,
I have some question regarding tcp/ip.
1. I tried to set-up an udp client-server application between my strongarm
platform and the PC. The server downloads an mpeg compressed stream to the
client-decoder after a request message. When the server starts to download,
the client send me the "recv out of MBUFS" error message. What could be the
reason? How can I trace the work of network threads to debug this problem?
2. Using a tcp/ip connection (that works) I noticed that the decoding time
of the mpeg3 decoder doubles if during the decoding the network threads are
active.
More clearly, the test I've done to understand why the mpeg3 decoder was not
real-time is the following:
- The client initializes the interfaces (init_all_network_interfaces)
- connects to the server
- starts decoding taking encoded frames from the memory
The decoding time in this case is double with respect to the secoding time I
get without the first two steps. Is it possible such a performance
decreasing only caused by the presence of network threads?
3. What's the difference in using Free instead of OpenBSD? Is there any
performance hints?
Thanks a lot for your help,
Andrea Acquaviva.
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2002-06-12 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 17:13 aacquaviva [this message]
2002-06-12 0:29 ` Andrew Lunn
2002-06-11 17:20 Dan Conti
2002-06-12 14:45 aacquaviva
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=200206120011.CAA15114@promet2.deis.unibo.it \
--to=aacquaviva@deis.unibo.it \
--cc=ecos-discuss@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).