From: Luciano Coelho <luciano.coelho@nokia.com>
To: ext Eric Dumazet <eric.dumazet@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Kristo Tero (Nokia-D/Tampere)" <Tero.Kristo@nokia.com>
Subject: Re: neigh_periodic_timer expires too often
Date: Wed, 05 Aug 2009 10:48:30 +0300 [thread overview]
Message-ID: <4A79394E.1030001@nokia.com> (raw)
In-Reply-To: <4A72E8A1.2070705@gmail.com>
ext Eric Dumazet wrote:
> Luciano Coelho a écrit :
>
>> Coelho Luciano (Nokia-D/Helsinki) wrote:
>>
>>> ext Eric Dumazet wrote:
>>>
>>>
>>>> So please test it and tell me/us you like it :)
>>>>
>>>>
>>> I applied your patch on top of the 2.6.28 I'm using and will start
>>> testing it now. I can also try to test it on top of 2.6.31-rc4 plus
>>> wireless-testing stuff, if needed.
>>>
>>> I'll tell you that I liked your patch in a moment (I actually already
>>> liked it, but I'll wait until I know it works before I tell you ;)
>>>
>>>
>> Just a small update. We have run some very basic tests with 2.6.28.
>> The patch seems to work fine and we don't see excessive wake-ups from
>> neigh anymore (thanks Tero for helping with the tests). We will still
>> run one of our full release test rounds in order to make sure that there
>> are no regressions. I'll let you know when we have some more results.
>>
>>
>
> Thanks for the update, I am running this patch on net-next-2.6 with no problem.
>
We have now run our release round tests and everything is working fine.
I'll report back if we find any issues with this change in the future
(which I really don't expect to happen ;).
Thank you very much for fixing this.
--
Cheers,
Luca.
next prev parent reply other threads:[~2009-08-05 7:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 10:44 neigh_periodic_timer expires too often Luciano Coelho
2009-07-30 13:15 ` Eric Dumazet
2009-07-30 14:33 ` Luciano Coelho
2009-07-31 12:22 ` Luciano Coelho
2009-07-31 12:50 ` Eric Dumazet
2009-08-05 7:48 ` Luciano Coelho [this message]
2009-08-03 1:35 ` David Miller
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=4A79394E.1030001@nokia.com \
--to=luciano.coelho@nokia.com \
--cc=Tero.Kristo@nokia.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).