public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: Gary Thomas <gary@chez-thomas.org>
Cc: eCos Discussion <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] TCP stack not delaying/piggybacking ACKs?
Date: Mon, 08 Jul 2002 16:29:00 -0000	[thread overview]
Message-ID: <20020708183316.A31984@visi.com> (raw)
In-Reply-To: <1026170335.15020.1426.camel@hermes.chez-thomas.org>; from gary@chez-thomas.org on Mon, Jul 08, 2002 at 05:18:54PM -0600

On Mon, Jul 08, 2002 at 05:18:54PM -0600, Gary Thomas wrote:

> > I'm working with an application that exchanges a continuous
> > stream of data with a host.  Each sends a TCP packet full of
> > data every 10ms or so.
> > 
> > The eCos stack is not delaying/piggybacking ACKs, so the eCos
> > app is sending roughly twice as many packets as it needs to.
> 
> This has never been mentioned before.  Which is not to say that
> it's working properly :-)

It's also possible I've broken something while mucking with the
stack.  I've replaced the IP checksum routine with assembly
language and made the TCP keepalive timer configurable at run
time.  I don't think either should have affected the ACK delay
mechanism, but that's what they all say...

> A couple of things to try:
>   * The new OpenBSD stack.  This would require updating to the
>     latest CVS.

I may try that, but it will have to wait a bit until I find and
fix the unrelated application bug I was looking for when I
noticed this.

>   * There may be a flag/switch in the FreeBSD stack (the one you
>     are using) which controls this, but it would require some time
>     to investigate.

I've been browsing around the sources and haven't quite figured
out how it's supposed to work.  I do have the TCP_NODELAY flag
set on the socket, but I don't know if that has anything to do
with it.  That is easy enough to test.

> How are you testing this (creating such an environment)?

It is, of course, rather complicated: There's a custom app and
device driver driver on the host end and so on.  I'll see if I
can come up with a simpler setup that also demonstrates the
behavior.

-- 
Grant Edwards
grante@visi.com

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

  reply	other threads:[~2002-07-08 23:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-08 16:13 Grant Edwards
2002-07-08 16:18 ` Gary Thomas
2002-07-08 16:29   ` Grant Edwards [this message]
2002-07-08 18:38     ` Mark Salter
2002-07-08 19:35       ` Grant Edwards
2002-07-09  9:13       ` Grant Edwards
2002-07-09 13:40         ` Mark Salter
2002-07-10  0:57         ` Martin Buck
2002-07-09  7:50   ` Wolfgang Heppner
2002-07-09  7:56     ` Gary Thomas

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=20020708183316.A31984@visi.com \
    --to=grante@visi.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gary@chez-thomas.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).