From: Andi Kleen <ak@suse.de>
To: Julian Anastasov <ja@ssi.bg>
Cc: "Milam, Chad" <Chad_Milam@nyc.yr.com>,
netdev@oss.sgi.com,
"Julian Anastasov <ja@ssi.bg>"
<IMCEANOTES-Julian+20Anastasov+20+3Cja+40ssi+2Ebg+3E@avee-health.com>
Subject: Re: dst cache overflow 2.2.x; x>=16
Date: Mon, 15 Apr 2002 21:53:15 +0200 [thread overview]
Message-ID: <20020415215315.A16910@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0204152232230.1201-100000@u.domain.uli>
> I mean when you see the dst cache overflow message can the
> command help? But ... may be are running a kernel patched with your
> changes. I'm asking this because I know cases where wrong changes
> can make problems with dst cache. But the plain kernel should be
> fine. One question more: can you say that this box is used only as
> router or what kind of TCP or UDP connections you have (to/from the
> box)? There can be some corner cases in the dst cache usage from
> connected sockets.
I would suspect CheckPoint (I think it has kernel modules, hasn't it)
We had a similar report of such a thing a few months ago and they were
using CheckPoint too.
-Andi
next prev parent reply other threads:[~2002-04-15 19:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-15 19:07 dst cache overflow 2.2.x; x>=16 Milam, Chad
2002-04-15 22:53 ` Julian Anastasov
2002-04-15 19:53 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-15 19:58 Milam, Chad
2002-04-15 21:47 ` Robert Olsson
2002-04-15 18:10 Milam, Chad
2002-04-15 18:27 ` jamal
2002-04-15 18:31 ` Julian Anastasov
2002-04-15 15:21 Milam, Chad
2002-04-15 17:53 ` jamal
2002-04-14 20:44 Milam, Chad
2002-04-14 20:53 ` jamal
2002-04-14 21:38 ` Robert Olsson
2002-04-14 20:25 Milam, Chad
2002-04-14 20:32 ` jamal
2002-04-14 20:38 ` jamal
2002-04-14 19:54 Milam, Chad
2002-04-14 20:04 ` jamal
2002-04-14 17:51 Milam, Chad
2002-04-14 19:39 ` jamal
2002-04-14 19:43 ` jamal
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=20020415215315.A16910@wotan.suse.de \
--to=ak@suse.de \
--cc=Chad_Milam@nyc.yr.com \
--cc=IMCEANOTES-Julian+20Anastasov+20+3Cja+40ssi+2Ebg+3E@avee-health.com \
--cc=ja@ssi.bg \
--cc=netdev@oss.sgi.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 NNTP newsgroup(s).