public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: James Hunter <jhunter@aptx.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Sockets getting full..
Date: Thu, 28 Jun 2007 08:38:00 -0000	[thread overview]
Message-ID: <20070627224522.GC8009@lunn.ch> (raw)
In-Reply-To: <8C4E0C2409735E4FBC22D754A238F94D5CD9CB@APTSBS.apt.local>

On Wed, Jun 27, 2007 at 11:25:32AM +0100, James Hunter wrote:
> Hi,
> 
> We are using a PowerQuicc III (MPC8541@677Mhz - so plenty of grunt)
> which is tasked with sending and receiving data over a UDP connection.
> The test application is only receiving data from another external UDP
> transmitter.
> 
> What we are seeing is almost immediately the socket is filling up with
> data as if your application is not reading the data back quickly enough.
> 
> 
> This test application spins on a Select() waiting to get packets, its
> executing around ~10k times per second so fast enough to catch any
> packets - we do sleep at the end of this loop.
> 
> The sending unit sends around 700 packets per second, however we receive
> only around 120 (going on the results returned by Select function).
> However the packets received are in order (using a sequence number) so
> nothing is dropped, they just appear to fall out of Select really really
> slow (we are aiming for a lot more than 700 packets per second from the
> HW)

I think we need to see the code in order to understand this....

  Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2007-06-27 22:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27 20:07 James Hunter
2007-06-28  8:38 ` Andrew Lunn [this message]
2007-06-28 15:12 James Hunter

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=20070627224522.GC8009@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=jhunter@aptx.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).