public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Alok Singh <aloks@broadcom.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Delay in procesing packet across the BSD stack -
Date: Fri, 01 Jun 2007 23:04:00 -0000	[thread overview]
Message-ID: <20070601230438.GG5944@lunn.ch> (raw)
In-Reply-To: <FE7FB54DCB7C6949A1D3F9FF22DA6C135DF89B@lvl7in-mail01.lvl7.com>

On Sat, Jun 02, 2007 at 04:30:00AM +0530, Alok Singh wrote:
> 
> Hi,
> I'm seeing a strange problem on my Box.? I'm using Free BSD stack. The issue is that when I send icmp requests from a single client to the box, the stack doesn't respond in time.? But when I start sending icmp requests from another client, the stack starts sending 100% ICMP echo replies.? I'm currently debugging the system. I've seen that if I send echo requests very slowly, then invariably client times out. When I send icmp request from another client, it sorts of kick something in the stack, and the echo reply to the previous request packet also comes out. ??
> 
> I'm debugging the system. But if you have some suggestions for me, let me know.

Check your interrupts are working correctly. It sounds like you are
loosing interrupts, probably TX complete, so the next packet is not
getting sent until the next RX happens.

        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-01 23:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01 23:00 Alok Singh
2007-06-01 23:04 ` Andrew Lunn [this message]
2007-06-02  0:16   ` Alok Singh
2007-06-02  0:18     ` Alok Singh
2007-06-02 14:29       ` Gary Thomas
2007-06-02 15:14         ` Alok Singh
2007-06-04  0:37         ` Alok Singh

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=20070601230438.GG5944@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=aloks@broadcom.com \
    --cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).