From: Luciano Coelho <luciano.coelho@nokia.com>
To: netdev@vger.kernel.org
Cc: tero.kristo@nokia.com
Subject: neigh_periodic_timer expires too often
Date: Thu, 30 Jul 2009 13:44:21 +0300 [thread overview]
Message-ID: <4A717985.7060909@nokia.com> (raw)
Hi,
We were making some measurements and trying to figure out which timers
in the kernel can be made deferrable so that our device doesn't have to
wake up too often.
During this investigation, we found out that the neigh_periodic_timer is
expiring approximately every 8 seconds, even when we don't have a
network connection established. After the connection is established,
the timer starts expiring every 2 seconds and continues to expire at
this interval after the connection is closed.
We have been converting many of the kernel times to deferrable timers.
Checking the netdev mailing list archives, I found out that this issue
has been discussed in December 2007 [1], but the thread seems to have
died out and the proposed patch has never been applied AFAICS.
Another proposed solution, which has never been applied either, was to
convert this timer from softirq-based to workqueue-based [2]. Would
that be any better?
So, my question is, does it make sense to make this timer deferrable or
use the workqueue instead? Or is there any other better solution to
avoid unnecessarily frequent wakeups caused by neigh_periodic_timer?
We are using a kernel based on 2.6.28.
[1] http://article.gmane.org/gmane.linux.network/81361
[2] http://article.gmane.org/gmane.linux.network/81140
--
Cheers,
Luca.
next reply other threads:[~2009-07-30 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 10:44 Luciano Coelho [this message]
2009-07-30 13:15 ` neigh_periodic_timer expires too often 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
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=4A717985.7060909@nokia.com \
--to=luciano.coelho@nokia.com \
--cc=netdev@vger.kernel.org \
--cc=tero.kristo@nokia.com \
/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).