From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3276 invoked by alias); 28 Oct 2009 17:02:38 -0000 Received: (qmail 3025 invoked by uid 22791); 28 Oct 2009 17:02:36 -0000 X-SWARE-Spam-Status: No, hits=0.0 required=5.0 tests=BAYES_50,SPF_PASS X-Spam-Check-By: sourceware.org Received: from smtrly02.smartm.com (HELO smtrly02.smartm.com) (65.249.22.140) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 28 Oct 2009 17:02:24 +0000 Received: from sr-fre-exch01.smartm.internal ([10.0.10.35]) by smtrly02.smartm.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 28 Oct 2009 10:00:19 -0700 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 28 Oct 2009 17:02:00 -0000 Message-ID: <9EFFCEC257D2B649BCD6495F5C704AA9090C479E@sr-fre-exch01.smartm.internal> In-Reply-To: References: From: "Carruth, Rusty" To: "Grant Edwards" , Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: RE: [ECOS] What causes interrupted network system calls? X-SW-Source: 2009-10/txt/msg00172.txt.bz2 In my experience with Solaris and Linux, you should ALWAYS check for EINTR and retry the operation. As I remember, you wouldn't get them often, but you could (and of course, it was always at the worst possible moment!). If I remember right (which may not be the case!). I don't suppose you have the Stevens book? What does it say about this? Rusty Rusty Carruth | CSE SSD Storage Products Division | SMART Modular Technologies Adtron Corporation | 4415 E. Cotton Center Blvd | Phoenix, AZ 85040 Office: 602-735-0300 | Fax: 602-735-0349 | Email: Rusty.Carruth@smartm.com | www.smartm.com =20 > -----Original Message----- > From: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss- > owner@ecos.sourceware.org] On Behalf Of Grant Edwards > Sent: Wednesday, October 28, 2009 9:06 AM > To: ecos-discuss@sources.redhat.com > Subject: [ECOS] What causes interrupted network system calls? >=20 > 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. >=20 > 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. >=20 > Is the frequent -EINTR return expected behavior for the new > stack? >=20 > 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? >=20 > -- -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss