From: Kelvin Lawson <klawson@ad-holdings.co.uk>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: Problems with ppp and Windows
Date: Thu, 17 Jun 2004 09:08:00 -0000 [thread overview]
Message-ID: <40D15F26.9050206@ad-holdings.co.uk> (raw)
In-Reply-To: <1087388654.29814.14.camel@famine>
Hi Ãyvind,
> Ah! progress!
Excellent!
> - eCos could be a bit more friendly with the developer when running out of memory. Perhaps
> there are suitable facilities for detecting these situations.
> In addition to the suggestions you made, perhaps it would be a good idea to add a fn that
> is invoked by the memory allocator when running out of memory? By default this could be
> an empty fn(handy breakpoint site), and the application could override it with something
> else(e.g. reset the board, invoke debugger, etc.).
Yes, sounds fine. In my case I'd be happy with just a debug message or
assert in cyg_net_malloc() when not enough memory is available. I would
think this should be a build option, rather than a default operation.
I think the proper place to add some debug notification is at the usage
points of network mallocs. In the case of PPP, after the MALLOC()
failed, it ought to have done something about it or printed some debug,
rather than just carrying on broken.
> - reduce memory requirements for PPP and freebsd networking stack.
For PPP there are a bunch of configuration options that aren't covered
by the cyg_ppp_options_t structure. I've added a few options here to
handle authorisation for dialin connections. Similarly you could extend
it to disable things like VJ compression to reduce the memory requirements.
> - It is a bit hard to *know* how much memory is required. It would be nice to have a simple
> way of figuring this out at compile time.
Difficult to gauge in advance I would think. Perhaps someone could
comment on where the default calculation comes from
(256*1024)+(MAXSOCKETS*1024) ? On my system this was enough for one
Ethernet device and plenty of connections. But it wasn't enough when
adding PPP to the mix (unless I disabled eth0).
Cheers,
Kelvin.
--
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:[~2004-06-17 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1087322512.28254.ezmlm@ecos.sourceware.org>
2004-06-15 21:36 ` [ECOS] " Øyvind Harboe
2004-06-16 9:55 ` [ECOS] " Kelvin Lawson
2004-06-16 12:24 ` [ECOS] " Øyvind Harboe
2004-06-17 9:08 ` Kelvin Lawson [this message]
2004-06-17 11:05 ` [ECOS] " Øyvind Harboe
2004-06-17 14:04 ` Kelvin Lawson
2004-04-22 15:14 [ECOS] " Øyvind Harboe
2004-06-15 10:30 ` [ECOS] " Kelvin Lawson
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=40D15F26.9050206@ad-holdings.co.uk \
--to=klawson@ad-holdings.co.uk \
--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).