From: Philip Thiem <witwerg@icequake.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] NEW imq driver
Date: Tue, 27 Jan 2004 14:28:23 +0000 [thread overview]
Message-ID: <6870000.1075213703@werg> (raw)
In-Reply-To: <002a01c3e466$bb7f8700$030aa8c0@t>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
[snip]
> I noticed that with my trafic counter. internal trafic grew to enormous
> levels 10X more than it can be. In reality there was almost no output at
> all.
> so DONT USE POLICERS ON EGRESS. on low trafic it is harmless but on
> 100mb/s it probably can kill computer (not tested).
>
> Seems imq have similar problem even if driver itself have no leaks kernel
> consumes all resousces on resnending droped packets so that computer stops
> responding
[snip]
Just curious, I suppose you had the same setup on the original IMQ? If not,
my point is moot. But if so and if the problem could be verified, it would
appear to me that there is less of a problem with the old patch(except
for features), and more of a problem with the inherent nature of what
is being attempting. Meaning that a set of assumptions made by the network
layer developers is being invalidated. For example, local outbound traffic
being policed instead of shaped.
Philip Thiem -- Icequake.net Administrator
Isn't it obvious lumberjacks love traffic lights?
GPG Pub Key Archived at wwwkeys.us.pgp.net
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-01-27 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 23:47 [LARTC] NEW imq driver Roy
2004-01-27 3:56 ` rubens
2004-01-27 4:33 ` Michael Renzmann
2004-01-27 4:42 ` Roy
2004-01-27 8:42 ` Andy Furniss
2004-01-27 14:28 ` Philip Thiem [this message]
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=6870000.1075213703@werg \
--to=witwerg@icequake.net \
--cc=lartc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.