netdev - Re: kernel 2.6.25-rc7 highly unstable on high load

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 28 Mar 2008 13:23:59 -0700
From:	Stephen Hemminger <stephen.hemminger@...tta.com>
To:	Eric Dumazet <dada1@...mosbay.com>
Cc:	Eric Dumazet <dada1@...mosbay.com>,
	Denys Fedoryshchenko <denys@...p.net.lb>,
	netdev@...r.kernel.org, netfilter-devel@...r.kernel.org
Subject: Re: kernel 2.6.25-rc7 highly unstable on high load

On Fri, 28 Mar 2008 16:57:55 +0100
Eric Dumazet <dada1@...mosbay.com> wrote:

> Eric Dumazet a écrit :
> > Denys Fedoryshchenko a écrit :
> >> Already patched and tested, it doesn't change anything.
> >>
> >>   
> >
> > We still leak dsts somewhere.
> >
> > You could try git bisect, or try to patch net/core/dst.c so that 
> > dst_gc_task() (line 83) displays
> > route informations for say 10 first entries found in the dst_busy_list
> > (refcnt, interface, source IP, dest IP, things like that) that could 
> > ring a bell given your netfilter rules or network conf.
> 
> I cooked a patch (untested) to implement this idea :
> 
> It should display lines similar to /proc/net/rt_cache (reusing the same 
> helper function)
> 
>

I wonder how much the route cache really helps when it grows so large?
Robert Olsson had suggested that turning it off when routing would help.
Perhaps the route cache is only really useful for local destinations? If the
cost of maintaining the route cache exceeds the cost of just using the existing
route table, there is no value to having a route cache.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html