On 2011-02-09 15:18, Glen Wernersbach wrote: > Jan, > > I think I figured out the send error. > > With RTNET I cannot receive and send on the same socket. > > So I cannot with RTNET do the follow that works with Linux: > 1. Socket > 2. SetSocketOpts > 3. Bind > 4. Listen > 5. Accept > 6. Recv > 7. Send > 8. close > ------ > > I can however with RTNET do the following: > 1. Socket > 2. SetSocketOpts > 3. Bind > 4. Listen > 5. Accept > 6. Recv > 7. Close > ------ > 8. Socket > 9. SetSocketOpts > 10. Bind > 11. Connect > 12. Send > 13. Close > > The second seemed to work. > > Does this makes sense to you?
Not yet. You once said accept() fails, but your setup starts to diverge after recv() (by doing a send()). What errors do which services return? Did you check that you have sufficient buffers configured for your network load (RTNET_RTIOC_EXTPOOL)? Again, it's _much_ easier if you stick this simple setup in a generic test case. Thanks, Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ RTnet-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rtnet-developers
