All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Denys Fedoryshchenko" <denys@visp.net.lb>
To: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: kernel 2.6.25-rc7 highly unstable on high load
Date: Sat, 29 Mar 2008 11:35:35 +0200	[thread overview]
Message-ID: <20080329093536.M90997@visp.net.lb> (raw)
In-Reply-To: <20080328.162137.132976647.davem@davemloft.net>

I checked whole night, shame on me. Seems this patch was curing the problem.
Probably it was rejected, and i didn't notice. I will be more careful, sorry 
again.

On Fri, 28 Mar 2008 16:21:37 -0700 (PDT), David Miller wrote
> From: Eric Dumazet <dada1@cosmosbay.com>
> Date: Fri, 28 Mar 2008 22:17:26 +0100
> 
> > Denys Fedoryshchenko a :
> > > It seems or patch change something (but it is just showing debug, 
strange), 
> > > or there is something fixed between 2.6.25-rc7-git1 and 2.6.25-rc7-
git3. LC-
> > > trie working fine, HASH also i cannot see any leaks.
> > 
> > Yes, the fix is the patch we mentioned yesterday, and you told us you 
tried it :(
> 
> Denys please be more careful in the future :-(
> 
> So much time and effort got wasted because of this.
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


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


  reply	other threads:[~2008-03-29  9:35 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
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 [this message]
     [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=20080329093536.M90997@visp.net.lb \
    --to=denys@visp.net.lb \
    --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.