All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Denys Fedoryshchenko" <denys@visp.net.lb>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: kernel 2.6.25-rc7 highly unstable on high load
Date: Fri, 28 Mar 2008 11:50:14 +0200	[thread overview]
Message-ID: <20080328094413.M11383@visp.net.lb> (raw)
In-Reply-To: <47ECA24C.10803@cosmosbay.com>

I will try do so, 


And i have a bit more information, not sure if it is useful. I took risk and 
running now one more loaded router, without nat this time. It has significant 
less load, but maybe i will catch something here also.

Here is dmesg i got
[   23.280155] dst_total: 4 delayed: 1 work_perf: 0 expires: 600 elapsed: 1 us
[   23.888719] dst_total: 5 delayed: 1 work_perf: 0 expires: 1600 elapsed: 1 
us
[   25.489486] dst_total: 11 delayed: 0 work_perf: 1 expires: 4294967295 
elapsed: 2 us
[   67.187254] dst_total: 23980 delayed: 1 work_perf: 0 expires: 600 elapsed: 
2 us
[   67.807126] dst_total: 24452 delayed: 1 work_perf: 0 expires: 1600 
elapsed: 3 us
[   69.453570] dst_total: 25103 delayed: 0 work_perf: 2 expires: 4294967295 
elapsed: 3 us
>>> here i run "ip route flush cache"
[  278.911357] dst_total: 16855 delayed: 2 work_perf: 0 expires: 600 elapsed: 
2 us
[  279.530432] dst_total: 16866 delayed: 2 work_perf: 0 expires: 1600 
elapsed: 1 us
[  281.197568] dst_total: 16901 delayed: 2 work_perf: 0 expires: 3100 
elapsed: 1 us
[  284.425797] dst_total: 16981 delayed: 2 work_perf: 0 expires: 4981 
elapsed: 1 us
[  289.665137] dst_total: 17067 delayed: 2 work_perf: 0 expires: 8000 
elapsed: 1 us
[  297.960978] dst_total: 17219 delayed: 2 work_perf: 0 expires: 11000 
elapsed: 1 us
[  309.379867] dst_total: 17426 delayed: 2 work_perf: 0 expires: 14100 
elapsed: 2 us
[  323.972039] dst_total: 17629 delayed: 2 work_perf: 0 expires: 18196 
elapsed: 2 us
[  342.831626] dst_total: 13563 delayed: 2 work_perf: 0 expires: 23000 
elapsed: 2 us
[  366.592260] dst_total: 13830 delayed: 2 work_perf: 0 expires: 28000 
elapsed: 2 us
[  395.753299] dst_total: 14142 delayed: 2 work_perf: 0 expires: 33000 
elapsed: 2 us
[  429.952513] dst_total: 13156 delayed: 3 work_perf: 0 expires: 600 elapsed: 
2 us
[  430.565783] dst_total: 13164 delayed: 3 work_perf: 0 expires: 1600 
elapsed: 1 us
[  432.267868] dst_total: 13184 delayed: 3 work_perf: 0 expires: 3100 
elapsed: 1 us
[  435.457375] dst_total: 13220 delayed: 3 work_perf: 0 expires: 5700 
elapsed: 2 us
[  441.355880] dst_total: 13279 delayed: 3 work_perf: 0 expires: 8000 
elapsed: 2 us
[  449.567527] dst_total: 13363 delayed: 3 work_perf: 0 expires: 11000 
elapsed: 1 us
[  461.027956] dst_total: 13507 delayed: 3 work_perf: 0 expires: 14000 
elapsed: 2 us
[  475.568361] dst_total: 12084 delayed: 3 work_perf: 0 expires: 18000 
elapsed: 2 us

Is expires values appearing 4294967295 normal?
Btw i am doing ip route flush cache only manually, normally it never happens 
on this machines.

On Fri, 28 Mar 2008 08:46:20 +0100, Eric Dumazet wrote
> Denys Fedoryshchenko :
> > 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.


--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.


  reply	other threads:[~2008-03-28  9:50 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-27  6:35 kernel 2.6.25-rc7 highly unstable on high load Denys Fedoryshchenko
2008-03-27  6:40 ` David Miller
2008-03-27  7:03   ` Eric Dumazet
2008-03-27  8:36     ` Denys Fedoryshchenko
2008-03-27  8:48     ` Denys Fedoryshchenko
2008-03-27 14:41     ` Denys Fedoryshchenko
2008-03-27 14:52       ` Eric Dumazet
     [not found]         ` <20080327151520.M89250@visp.net.lb>
2008-03-27 16:07           ` Eric Dumazet
2008-03-27 16:29             ` Eric Dumazet
2008-03-27 18:37             ` Denys Fedoryshchenko
2008-03-27 18:56               ` Eric Dumazet
2008-03-27 19:05                 ` Denis V. Lunev
2008-03-27 22:03                 ` David Miller
2008-03-28  0:47                   ` Denys Fedoryshchenko
2008-03-28  4:50                   ` Denys Fedoryshchenko
2008-03-28  5:25                   ` Denys Fedoryshchenko
2008-03-28  5:49                     ` Eric Dumazet
2008-03-28  7:38                       ` Denys Fedoryshchenko
2008-03-28  7:46                         ` Eric Dumazet
2008-03-28  9:50                           ` Denys Fedoryshchenko [this message]
2008-03-28 15:57                           ` Eric Dumazet
2008-03-28 20:23                             ` Stephen Hemminger
2008-03-28 20:45                               ` Denys Fedoryshchenko
2008-03-28 21:17                                 ` Eric Dumazet
2008-03-28 23:21                                   ` David Miller
2008-03-29  9:35                                     ` Denys Fedoryshchenko
     [not found]                                   ` <20080328220902.M5377@visp.net.lb>
2008-03-29  8:31                                     ` Eric Dumazet
2008-03-27  7:07   ` Denys Fedoryshchenko
2008-03-27 15:01   ` Patrick McHardy

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=20080328094413.M11383@visp.net.lb \
    --to=denys@visp.net.lb \
    --cc=dada1@cosmosbay.com \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@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.