From: Phil Oester <kernel@linuxace.com>
To: buakaw@buakaw.homelinux.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: dst cache overflow
Date: Tue, 22 Mar 2005 08:16:57 -0800 [thread overview]
Message-ID: <20050322161657.GA18925@linuxace.com> (raw)
In-Reply-To: <1297.192.168.0.37.1111480783.squirrel@buakaw.homelinux.net>
On Tue, Mar 22, 2005 at 10:39:43AM +0200, buakaw@buakaw.homelinux.net wrote:
>
> computer's main job is to be router on small LAN with 10 users and some
> services like qmail, apache, proftpd, shoutcast, squid, and ices on slack
> 10.1. Iptables and tc are used to limit bandwiwdth and the two bandwidthd
> daemons are running on eth0 interface and all the time the cpu is used at
> about 0.4% and additional 12% by ices when encoding mp3 on demand, and
> the proccess ksoftirqd/0 randomally starts to use 100% of 0 cpu in normal
> situation and one time when the ksoftirqd/0 became crazy i noticed dst
> cache overflow messages in syslog but there are more of thies lines in
> logs about 5 times in 10 days period
There was a problem fixed in the handling of fragments which caused dst
cache overflow in the 2.6.11-rc series. Are you still seeing dst cache
overflow on 2.6.11?
Phil
next prev parent reply other threads:[~2005-03-22 16:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-20 20:51 buakaw
2005-03-22 3:40 ` dst cache overflow Andrew Morton
2005-03-22 8:39 ` buakaw
2005-03-22 16:16 ` Phil Oester [this message]
2005-03-22 17:07 ` buakaw
2005-03-22 21:12 ` Eric Dumazet
2005-03-22 22:14 ` buakaw
2005-03-23 6:21 ` Eric Dumazet
-- strict thread matches above, loose matches on Subject: below --
2007-08-14 16:06 Tobias Diedrich
2007-08-14 17:24 ` Eric Dumazet
2007-08-14 18:00 ` Tobias Diedrich
2007-08-16 16:45 ` Eric Dumazet
2007-12-14 17:29 ` Tobias Diedrich
2007-12-15 6:29 ` Herbert Xu
2007-12-15 10:08 ` Tobias Diedrich
2007-12-16 7:35 ` Herbert Xu
2007-12-16 8:38 ` Tobias Diedrich
2008-03-17 1:25 ` Tobias Diedrich
2008-03-18 18:59 ` Tobias Diedrich
2008-10-13 13:54 Oleksandr Samoylyk
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=20050322161657.GA18925@linuxace.com \
--to=kernel@linuxace.com \
--cc=buakaw@buakaw.homelinux.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox