From: "Ken Yee" <kenkyee@excite.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] any way to reset the TCP/IP network buffers in ecos?
Date: Thu, 20 Sep 2012 17:54:00 -0000 [thread overview]
Message-ID: <20120920135429.21498@web005.roc2.bluetie.com> (raw)
On our system, we bring PPP up and down to minimize connection time costs, but after running a while, we seem to get this error:
socket returned: No buffer space available
The error message is what's returned from the system strerror() call which maps errno to a message.
And what it's doing is a simple socket creation call to get ready to send a packet:
s = socket(AF_INET, SOCK_RAW, p->p_proto);
So is there any way to reset the network buffers inside eCos?
We can do this every time ppp is brought down since no other networking takes place while the link is down...
ken
--
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 reply other threads:[~2012-09-20 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 17:54 Ken Yee [this message]
2012-09-21 5:11 ` Bernd Edlinger
2012-09-21 12:57 Ken Yee
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=20120920135429.21498@web005.roc2.bluetie.com \
--to=kenkyee@excite.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).