From: Hugo Tyson <hmt@redhat.com>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] TCP/IP large packets -errors
Date: Fri, 20 Apr 2001 07:15:00 -0000 [thread overview]
Message-ID: <wwtwv8feklo.fsf@masala.cambridge.redhat.com> (raw)
In-Reply-To: <00b201c0c996$16d81070$1400a8c0@rts.com.pl>
"=?iso-8859-2?B?TWFyZWsgo7Fja2k=?=" <lacki@rts.com.pl> writes:
> I have a problem with stack TCP or network card driver (NE200) on platform
> i386.
> Stack works correctly if i send packets less than 1500 bytes. When I send
> more than 1500 bytes for example 1600 bytes ( tested on ping ), eCos
> responses for first part (1500 bytes) and dosen't response for next
> parts(100bytes). Then if i send later less than 1500 bytes ,eCos response
> for request and send extra this 100 bytes from first large frame.
> What's happend ?????
Bigger pings work fine with ARMs and i82559 or LAN91C96 &c. They split
into several smaller packets, and are sent back OK.
You don't say what release you're using.
There was a problem ages ago with the reassembly of those ICMP fragments,
to do with the alignment of MBUFs causing a macro not to work.
Astonishingly it only affected ICMP fragments! Here's the ChangLog entry.
2000-06-23 Hugo Tyson <hmt@cygnus.co.uk>
* src/ecos/support.c (cyg_net_mbuf_alloc, cyg_kmem_init): Align
the mbuf pool to MSIZE [128] bytes. That way dtom() works, nasty
though it is. That's needed for ip reassembly in ip_input.c, when
dealing with large icmp-layer packets eg. ping -s 2000 ...
Ensure you have that change.
It could be that your driver (I guess you're writing the ether driver) is
not correctly handling multiple queued-up send requests, if the packets are
eventually getting out when another rx occurs.
- Huge
next prev parent reply other threads:[~2001-04-20 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-20 5:25 Marek Łącki
2001-04-20 6:20 ` Lewin A.R.W. Edwards
2001-04-20 7:15 ` Hugo Tyson [this message]
2001-04-24 20:40 ` Andrew Lunn
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=wwtwv8feklo.fsf@masala.cambridge.redhat.com \
--to=hmt@redhat.com \
--cc=ecos-discuss@sources.redhat.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).