From: "Jürgen Lambrecht" <J.Lambrecht@televic.com>
To: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Cc: "Jürgen Lambrecht" <jurgen.lambrecht@scarlet.be>
Subject: [ECOS] max IP packet size = 9216 B. Why?
Date: Tue, 12 Jun 2007 21:58:00 -0000 [thread overview]
Message-ID: <466EC08A.8090704@televic.com> (raw)
Hello,
I found out that the maximum IP packet size = 9216 B (0x2400).
I implemented an echo program, both udp and tcp.
My ecos applic can receive more that 9216B, but not send back more than
that.
Has anybody a clue how to solve this?
I need to support the maximum IP packet size of 65535 B (IP_MAXPACKET).
I don't know if this is a bug in ecos, or a (hidden?) limitation of an
embedded OS.
Thanks,
Juergen Lambrecht
P.S.:
I'm busy tracing this back in the source
This comes from the socket that is allocated statically in
/io/fileio/.../fd.cxx and socket is part of a cyg_file (cyg_file is
defined by file in file.h). In cyg_file there is a member f_data, which
is the socket.
I'm continuing my search in the code at this point....
--
Jürgen Lambrecht
R&D Engineer
Televic Transport Systems
http://www.televic.com
Televic NV / SA (main office)
Leo Bekaertlaan 1
B-8870 Izegem
Tel: +32 (0)51 303045
Fax: +32 (0)51 310670
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2007-06-12 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 21:58 Jürgen Lambrecht [this message]
2007-06-12 22:12 ` Andrew Lunn
2007-06-12 22:46 ` Jürgen Lambrecht
2007-06-12 23:03 ` Andrew Lunn
2007-06-13 14:24 ` Jürgen Lambrecht
2007-06-13 15:44 ` Andrew Lunn
[not found] ` <058cebc1-1c19-438d-b5de-2c8015835c36@googlegroups.com>
2017-06-20 10:29 ` Jürgen Lambrecht
2017-06-23 10:32 ` Jürgen Lambrecht
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=466EC08A.8090704@televic.com \
--to=j.lambrecht@televic.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=jurgen.lambrecht@scarlet.be \
/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).