From: Grant Edwards <grant.b.edwards@gmail.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: What causes interrupted network system calls?
Date: Wed, 28 Oct 2009 18:05:00 -0000 [thread overview]
Message-ID: <hca13i$srj$1@ger.gmane.org> (raw)
In-Reply-To: <m3y6mv2ynp.fsf@xl5.calivar.com>
On 2009-10-28, Nick Garnett <nickg@ecoscentric.com> wrote:
> Grant Edwards <grant.b.edwards@gmail.com> writes:
>
>> 1) in the same situation we never saw EINTR with the previous
>> network stack.
>
> It is probable that the OpenBSD stack totally ignored signals
> and therefore wouldn't necessarily do the right thing. The
> FreeBSD stack is better integrated with POSIX support.
We're not using POSIX support.
>> 2) EINTR isn't listed as one of the possible return values for
>> send(), but we seem to be getting it:
>> http://ecos.sourceware.org/docs-3.0/ref/net-common-tcpip-manpages-send.html
>
> Very weird. The current FreeBSD documentation also does not
> mention EINTR. However Linux man pages do, as does the POSIX
> standard.
>
> In general net stack calls return EINTR only if the thread is
> broken out of a wait by cyg_thread_release(), and only POSIX
> signal handling generally does that.
We don't have any of the POSIX support enabled.
> If the application is using signals,
AFAIK, it isn't.
> then maybe the signal masks need to be set up differently.
I've just been told that retrying doesn't seem to help. Once
you get an -EINTR, it will happen 5-10 times in a row.
--
Grant Edwards grante Yow! Did you move a lot of
at KOREAN STEAK KNIVES this
visi.com trip, Dingy?
--
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:[~2009-10-28 18:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 16:06 [ECOS] " Grant Edwards
2009-10-28 17:02 ` Carruth, Rusty
2009-10-28 17:15 ` [ECOS] " Grant Edwards
2009-10-28 17:53 ` Nick Garnett
2009-10-28 18:05 ` Grant Edwards [this message]
2009-10-28 18:27 ` Nick Garnett
2009-10-28 18:40 ` Grant Edwards
2009-10-29 18:34 ` Grant Edwards
2009-10-29 18:53 ` Nick Garnett
2009-10-29 19:04 ` Grant Edwards
2009-10-28 18:33 ` Grant Edwards
2009-10-28 18:41 ` Nick Garnett
2009-10-28 18:15 ` Carruth, Rusty
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='hca13i$srj$1@ger.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=ecos-discuss@sources.redhat.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).