From: "Jürgen Lambrecht" <J.Lambrecht@televic.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Juergen Lambrecht <Jurgen.Lambrecht@scarlet.be>,
ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] max IP packet size = 9216 B. Why?
Date: Wed, 13 Jun 2007 14:24:00 -0000 [thread overview]
Message-ID: <466FEF53.1060909@televic.com> (raw)
In-Reply-To: <20070612215839.GX26816@lunn.ch>
Thanks Andrew! This solves it.
So the maximum supported IP packet size for an UDP socket is a configuration option. But you must be a TCP/IP networking expert to know about the option..
For anybody's information: to send/receive maximum sized UDP packets you have to setsockopt() SO_SNDBUF & SO_RCVBUF.
The maximum IP packet size is 65535 B, so the maximum UDP payload is 65507 B.
So it has no use to set SO_SNDBUF (for an UDP socket) higher than that value (65507 B).
Mark that SO_RCVBUF must be set to 65539 B to be able to receive the 65535 B IP packets (using UDP)!
For the ping test, ecos is configured OK for 65535 B IP-ping packets
I still have to test TCP, but TCP should adapt its buffers automatically.
Andrew Lunn wrote:
>>sendto returns the error code 322 or EMSGSIZE "Message too long".
>>I forgot to tell that's because the high water level of the send socket
>>(o->so_snd.sb_hiwat) is 9216 B (=0x2400) (in file
>>bsd_tcpip/current/src/sys/kern/uipc_socket.c:523).
>>
>>I will try to increase the socket's high water level (after I have found
>>where it is set ;-).
The high water level is set in bsd_tcpip/current/src/sys/netinet/udp_usrreq.c line 769.
Changing it here solves my problem.
>
>
> I think you can set it with setsockopt(). The option names are
Indeed! But I though you would then change so->so_snd.sb_mbmax in stead of so->so_snd.sb_hiwat.
With those options, I indeed changed the high water level. So the ecos patch above is wrong.
> SO_SNDBUF & SO_RCVBUF. However, there might be a system check to
> ensure they are not too large.
How can you know wat the allowed maximum is? I guess that is the value of so->so_snd.sb_mbmax that was set default to 73728 (as I saw with the debugger).
That maximum is probably related to the options CYGPKG_NET_MEM_USAGE, ...
You can of course check the return value of setsockopt().
Thank you again,
Juergen
>
> 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
next prev parent reply other threads:[~2007-06-13 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 21:58 Jürgen Lambrecht
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 [this message]
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=466FEF53.1060909@televic.com \
--to=j.lambrecht@televic.com \
--cc=Jurgen.Lambrecht@scarlet.be \
--cc=andrew@lunn.ch \
--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).