From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Paweł Staszewski" <pstaszewski@itcare.pl>
Cc: pstaszewski@artcom.pl, e1000-devel@lists.sourceforge.net,
netdev@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org,
bruce.w.allan@intel.com, jesse.brandeburg@intel.com,
stable@kernel.org, john.ronciak@intel.com,
jeffrey.t.kirsher@intel.com, bugme-daemon@bugzilla.kernel.org,
akpm@linux-foundation.org, David Miller <davem@davemloft.net>
Subject: Re: [Bugme-new] [Bug 15239] New: Problem with network performance after a while.
Date: Tue, 09 Feb 2010 08:36:17 +0100 [thread overview]
Message-ID: <1265700977.4236.127.camel@edumazet-laptop> (raw)
In-Reply-To: <4B710C93.9010603@itcare.pl>
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.
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
next prev parent reply other threads:[~2010-02-09 7:36 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 [this message]
2010-02-09 7:46 ` Paweł Staszewski
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=1265700977.4236.127.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bruce.w.allan@intel.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pstaszewski@artcom.pl \
--cc=pstaszewski@itcare.pl \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox