This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
What causes interrupted network system calls?
- From: Grant Edwards <grant dot b dot edwards at gmail dot com>
- To: ecos-discuss at sources dot redhat dot com
- Date: Wed, 28 Oct 2009 16:05:49 +0000 (UTC)
- Subject: [ECOS] What causes interrupted network system calls?
Somebody working on a network-intensive eCos application
reported to me that in situations where there are frequent
connection open/close operations, the various socket-related
system calls (send, connect, etc.) are frequently returning
-EINTR.
This application was recently ported from the old NetBSD
network stack to the FreeBSD stack, and the -EINTR return
values were never seen with the old stack.
Is the frequent -EINTR return expected behavior for the new
stack?
Is there a way to get the stack to restart system calls, or is
application code required to check for -EINTR and retry system
calls?
--
Grant Edwards grante Yow! I'm continually AMAZED
at at th'breathtaking effects
visi.com of WIND EROSION!!
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss