netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Stone <daniel@fooishbar.org>
To: Robert Olsson <Robert.Olsson@data.slu.se>
Cc: netdev@oss.sgi.com
Subject: Re: net/ipv4/route.c GC patch: is this insane?b4Db3tL
Date: Mon, 31 May 2004 22:26:08 +1000	[thread overview]
Message-ID: <20040531122608.GR24955@fooishbar.org> (raw)
In-Reply-To: <16571.9006.703294.10134@robur.slu.se>

[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]

On Mon, May 31, 2004 at 02:21:02PM +0200, Robert Olsson wrote:
> Daniel Stone writes:
>  > Hi guys,
>  > Attached is a patch to net/ipv4/route.c (against 2.4.23, sorry) to
>  > combat the 'dst cache full' issue. Essentially, there's a machine that I
>  > have access to (a router) that will report 'dst cache full', and
>  > immediately cease dealing with any IPv4 traffic. I found the attached
>  > patch against 2.0, and forward-ported it to 2.4. As this issue only
>  > crops up randomly every couple of weeks, I can't tell you whether it's
>  > worked or not. All I know is that it hasn't eaten my firstborn so far:
>  > given a quick spin, it seemed to work OK, but whether or not it solves
>  > the problem is a different matter.
> 
>  Hello!
> 
>  If your traffic is sane and you got dst cache overflow you should 
>  probably try to reduce gc_min_interval so your GC can release a 
>  higher numbers of dst entries per second. Flushing active entries
>  means that they are created again. This decreases your throughput
>  maybe just enough not to reach the limit where you reach overflow.

gc_min_interval was zero - should this increase, or what?.

>  > +	atomic_set(&ipv4_dst_ops.entries, 0);
> 
>  These counters should only be handled by the freeing process rt_free etc.

OK.

Thanks for the pointers!
:) d

-- 
Daniel Stone                                              <daniel@fooishbar.org>
"The programs are documented fully by _The Rise and Fall of a Fooish Bar_,
available by the Info system." -- debian/manpage.sgml.ex, dh_make template

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-05-31 12:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-30 15:14 net/ipv4/route.c GC patch: is this insane? Daniel Stone
2004-05-31 12:21 ` Robert Olsson
2004-05-31 12:26   ` Daniel Stone [this message]
2004-05-31 12:43     ` net/ipv4/route.c GC patch: is this insane?b4Db3tL Robert Olsson
2004-05-31 14:08       ` net/ipv4/route.c GC patch: is this insane? Daniel Stone
2004-05-31 15:06         ` Robert Olsson

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=20040531122608.GR24955@fooishbar.org \
    --to=daniel@fooishbar.org \
    --cc=Robert.Olsson@data.slu.se \
    --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).