From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19633 invoked by alias); 28 Jun 2007 08:38:54 -0000 Received: (qmail 19625 invoked by uid 22791); 28 Jun 2007 08:38:53 -0000 X-Spam-Check-By: sourceware.org Received: from mailgate.aptx.com (HELO mailgate.aptx.com) (83.141.98.202) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 28 Jun 2007 08:38:51 +0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 28 Jun 2007 15:12:00 -0000 Message-ID: <8C4E0C2409735E4FBC22D754A238F94D5CD9D1@APTSBS.apt.local> From: "James Hunter" To: "Andrew Lunn" Cc: X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: RE: [ECOS] Sockets getting full.. X-SW-Source: 2007-06/txt/msg00268.txt.bz2 > -----Original Message----- > From: Andrew Lunn [mailto:andrew@lunn.ch]=20 > Sent: 27 June 2007 23:45 > To: James Hunter > Cc: ecos-discuss@ecos.sourceware.org > Subject: Re: [ECOS] Sockets getting full.. >=20 > On Wed, Jun 27, 2007 at 11:25:32AM +0100, James Hunter wrote: > > Hi, > >=20 > > We are using a PowerQuicc III (MPC8541@677Mhz - so plenty of grunt)=20 > > which is tasked with sending and receiving data over a UDP=20 > connection. > > The test application is only receiving data from another=20 > external UDP=20 > > transmitter. > >=20 > > What we are seeing is almost immediately the socket is=20 > filling up with=20 > > data as if your application is not reading the data back=20 > quickly enough. > >=20 > >=20 > > This test application spins on a Select() waiting to get=20 > packets, its=20 > > executing around ~10k times per second so fast enough to catch any=20 > > packets - we do sleep at the end of this loop. > >=20 > > The sending unit sends around 700 packets per second, however we=20 > > receive only around 120 (going on the results returned by=20 > Select function). > > However the packets received are in order (using a sequence=20 > number) so=20 > > nothing is dropped, they just appear to fall out of Select really=20 > > really slow (we are aiming for a lot more than 700 packets=20 > per second=20 > > from the > > HW) >=20 > I think we need to see the code in order to understand this.... >=20 > Andrew >=20 Hi, We resolved the issue, appears to be some legacy i2c code that was causing us problems. Thanks, James. -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss