From: "Paweł Staszewski" <pstaszewski@itcare•pl>
To: Eric Dumazet <eric.dumazet@gmail•com>
Cc: David Miller <davem@davemloft•net>,
akpm@linux-foundation•org, netdev@vger•kernel.org,
e1000-devel@lists•sourceforge.net,
bugzilla-daemon@bugzilla•kernel.org,
bugme-daemon@bugzilla•kernel.org, jeffrey.t.kirsher@intel•com,
jesse.brandeburg@intel•com, bruce.w.allan@intel•com,
alexander.h.duyck@intel•com, peter.p.waskiewicz.jr@intel•com,
john.ronciak@intel•com, pstaszewski@artcom•pl, stable@kernel•org
Subject: Re: [Bugme-new] [Bug 15239] New: Problem with network performance after a while.
Date: Tue, 09 Feb 2010 08:46:02 +0100 [thread overview]
Message-ID: <4B7112BA.2020700@itcare.pl> (raw)
In-Reply-To: <1265700977.4236.127.camel@edumazet-laptop>
W dniu 2010-02-09 08:36, Eric Dumazet pisze:
> Le mardi 09 février 2010 à 08:19 +0100, Paweł Staszewski a écrit :
>
>> W dniu 2010-02-08 23:55, David Miller pisze:
>>
>>> From: Andrew Morton<akpm@linux-foundation•org>
>>> Date: Mon, 8 Feb 2010 14:15:13 -0800
>>>
>>>
>>>
>>>> That would be bad. That's a regression in 2.6.33-rc, and we've
>>>> backported that regression into 2.6.32.x -stable.
>>>>
>>>>
>>> Luckily we have a fix already. :-)
>>>
>>>
>> Yes - i make bugreport and after i write also here on the list
>>
>> And Eric Dumazet help to solve problem with "route cache" - and locking
>> load on one cpu after information about "route cache disabled".
>>
>> After his patch i don't see any errors in dmesg.
>>
>>
> OK, but this is real old bug (since 2.6.24), not a 2.6.32/2.6.33
> regression...
>
> You were just lucky not hitting it before, probably because you tried
> different settings.
>
>
>
Yes i think it was all about change of settings.
I start to search what settings will be the best - with some experiments
- about what will happen if....
> --
> 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
>
>
>
next prev parent reply other threads:[~2010-02-09 7:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15239-10286@http.bugzilla.kernel.org/>
2010-02-08 22:15 ` [Bugme-new] [Bug 15239] New: Problem with network performance after a while Andrew Morton
2010-02-08 22:55 ` David Miller
2010-02-09 7:19 ` Paweł Staszewski
2010-02-09 7:36 ` Eric Dumazet
2010-02-09 7:46 ` Paweł Staszewski [this message]
2010-02-08 23:06 ` Brandeburg, Jesse
2010-02-08 23:14 ` David Miller
2010-02-09 7:37 ` Paweł Staszewski
[not found] ` <20100208141537.babeed5f.akpm@linux-foundation.org>
2010-02-08 22:51 ` Rafael J. Wysocki
2010-02-08 22:58 ` David Miller
2010-02-08 23:04 ` Rafael J. Wysocki
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=4B7112BA.2020700@itcare.pl \
--to=pstaszewski@itcare$(echo .)pl \
--cc=akpm@linux-foundation$(echo .)org \
--cc=alexander.h.duyck@intel$(echo .)com \
--cc=bruce.w.allan@intel$(echo .)com \
--cc=bugme-daemon@bugzilla$(echo .)kernel.org \
--cc=bugzilla-daemon@bugzilla$(echo .)kernel.org \
--cc=davem@davemloft$(echo .)net \
--cc=e1000-devel@lists$(echo .)sourceforge.net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=jeffrey.t.kirsher@intel$(echo .)com \
--cc=jesse.brandeburg@intel$(echo .)com \
--cc=john.ronciak@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=peter.p.waskiewicz.jr@intel$(echo .)com \
--cc=pstaszewski@artcom$(echo .)pl \
--cc=stable@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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