From: andrew.lunn@ascom.ch (Andrew Lunn)
To: gthomas@redhat.com (Gary Thomas)
Cc: carl@leg.uct.ac.za, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] high bandwidth network problems
Date: Wed, 06 Sep 2000 05:19:00 -0000 [thread overview]
Message-ID: <200009061219.OAA01342@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <XFMail.20000906061319.gthomas@redhat.com>
> Try increasing the number of mbufs. Set the configuration parameter
> CYGPKG_NET_MEM_USAGE to something larger (the default is 256*1024).
>
> Do you have the latest code from CVS? I seem to recall something in there
> about an mbuf memory leak which was fixed recently. This might help.
Increasing the memory is not the real solution. The code will cope
with running out of mbufs, its a normal occurance. Whats wrong is
printing these messages. Printing these messages is a classic denial
of service problem. What it should do is limit the number of times it
prints it, to a maximum of one per second, or even not at all.
Andrew
next prev parent reply other threads:[~2000-09-06 5:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-06 2:58 Carl van Schaik
2000-09-06 5:13 ` Gary Thomas
2000-09-06 5:19 ` Andrew Lunn [this message]
2000-09-06 5:24 ` Gary Thomas
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=200009061219.OAA01342@biferten.ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=carl@leg.uct.ac.za \
--cc=ecos-discuss@sources.redhat.com \
--cc=gthomas@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).