From: Simon Kallweit <simon.kallweit@intefo.ch>
To: Sergei Gavrikov <sergei.gavrikov@gmail.com>
Cc: ecos-devel@ecos.sourceware.org
Subject: lwip 1.3.1 testing
Date: Tue, 25 Aug 2009 07:41:00 -0000 [thread overview]
Message-ID: <4A939599.8040703@intefo.ch> (raw)
In-Reply-To: <4A938008.70909@intefo.ch>
[-- Attachment #1: Type: text/plain, Size: 1514 bytes --]
Hi
I have done a new lwip test release with the following changes:
* incorporated Sergei's patch (ctrl-c support)
* added an lwip_eth_simple and lwip_eth_sequential template
The new test release can be downloaded from
http://download.westlicht.ch/lwip-20090825.tar.gz
To do synth tests do the following:
create a new configuration:
> ecosconfig new linux lwip_eth_simple
or:
> ecosconfig new linux lwip_eth_sequential
enable eth0 synth device (file is attached):
> ecosconfig import eth_synth.ecm
build:
> make
> make -C build/net/lwip_tcpip/current tests
run tests (a sample target.tdf is attached):
./build/install/tests/net/lwip_tcpip/current/tests/httpd_simple -t
target.tdf -io -nw
The current templates use DHCP to get an IP address. Just reconfigure
for static IPs.
To do some stress testing you can run the nc_test_slave testcase (only
available in sequential mode). You will need the corresponding master
test, which can be found in the ecos repository under
packages/net/common/current/tests
To build the nc_test_master go to the upper directory and type:
> make -f make.host
Also you should loosen up the very conservative default configuration of
lwip pbufs to avoid dropped packets:
> ecosconfig import pbufs.ecm
> make && make -C build/net/lwip_tcpip/current tests
Testing on real hardware would be especially useful. Also testing on
big-endian targets might reveal some issues, as I've only been testing
on little-endian platforms.
Thanks a lot for testing!
Simon
[-- Attachment #2: eth_synth.ecm --]
[-- Type: text/plain, Size: 63 bytes --]
cdl_option CYGVAR_DEVS_ETH_ECOSYNTH_ETH0 {
user_value 1
};
[-- Attachment #3: target.tdf --]
[-- Type: text/plain, Size: 61 bytes --]
synth_device ethernet {
eth0 real eth1
logging 0
}
[-- Attachment #4: pbufs.ecm --]
[-- Type: text/plain, Size: 118 bytes --]
cdl_option CYGNUM_LWIP_TCP_MSS {
user_value 512
};
cdl_option CYGNUM_LWIP_PBUF_POOL_SIZE {
user_value 64
};
next prev parent reply other threads:[~2009-08-25 7:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 7:11 Simon Kallweit
2009-08-21 7:43 ` John Dallaway
2009-08-21 9:12 ` Edgar Grimberg
2009-08-21 18:43 ` Sergei Gavrikov
2009-08-24 20:18 ` Sergei Gavrikov
2009-08-25 6:09 ` Simon Kallweit
2009-08-25 7:41 ` Simon Kallweit [this message]
2009-08-25 12:08 ` Sergei Gavrikov
2009-08-25 20:33 ` Sergei Gavrikov
2009-08-26 6:38 ` Simon Kallweit
2009-08-26 8:43 ` Sergei Gavrikov
2009-08-26 20:46 ` Sergei Gavrikov
2009-08-27 7:17 ` Simon Kallweit
2009-08-27 8:03 ` Sergei Gavrikov
2009-10-25 16:46 ` John Dallaway
2009-10-26 13:00 ` Simon Kallweit
2009-10-26 13:54 ` John Dallaway
2009-10-26 14:29 ` Simon Kallweit
2009-10-26 17:13 ` John Dallaway
2009-10-27 13:06 ` Simon Kallweit
2009-11-20 10:24 ` John Dallaway
2009-12-07 13:41 ` Simon Kallweit
2009-12-17 10:45 ` John Dallaway
2010-01-19 12:07 ` John Dallaway
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=4A939599.8040703@intefo.ch \
--to=simon.kallweit@intefo.ch \
--cc=ecos-devel@ecos.sourceware.org \
--cc=sergei.gavrikov@gmail.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).