From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19843 invoked by alias); 12 Jun 2002 00:20:28 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 19825 invoked from network); 12 Jun 2002 00:20:26 -0000 Received: from unknown (HELO bunker.fullplaymedia.com) (63.165.188.8) by sources.redhat.com with SMTP; 12 Jun 2002 00:20:26 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Tue, 11 Jun 2002 17:20:00 -0000 Message-ID: From: "Dan Conti" To: Subject: RE: [ECOS] udp problem & network stack questions X-SW-Source: 2002-06/txt/msg00178.txt.bz2 As far as the 'eth_recv out of MBUFS' error message, usually it's caused by leaving a socket open. I.e. you have a socket that is receiving incoming data, but you're not reading off it, so the data gets buffered up. The easiest way to get around it is to increase the amount of memory reserved for MBUFs (this is in the network settings in the config tool). When i saw this last, i noticed that a single socket could use all the available memory for MBUFs. For item number 2, if you have a lot of network traffic you might see a performance hit once your network is initialized. 50% is a bit much, especially on a strongarm; i guess i'd be curious as to how much broadcast/multicast traffic you are getting. On item number 3 i would assume you are talking about the networking stacks; i dont have much insight into either, sorry. -----Original Message----- From: aacquaviva@deis.unibo.it [mailto:aacquaviva@deis.unibo.it] Sent: Tuesday, June 11, 2002 5:12 PM To: ecos-discuss@sources.redhat.com Subject: [ECOS] udp problem & network stack questions Hi, I have some question regarding tcp/ip. 1. I tried to set-up an udp client-server application between my strongarm=20 platform and the PC. The server downloads an mpeg compressed stream to the=20 client-decoder after a request message. When the server starts to download,=20 the client send me the "recv out of MBUFS" error message. What could be the=20 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=20 of the mpeg3 decoder doubles if during the decoding the network threads are=20 active. More clearly, the test I've done to understand why the mpeg3 decoder was not=20 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=20 get without the first two steps. Is it possible such a performance=20 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?=20=20=20 Thanks a lot for your help, Andrea Acquaviva. --=20 Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss