From: Eric Dumazet <dada1@cosmosbay.com>
To: Tero.Kristo@nokia.com
Cc: netdev@vger.kernel.org
Subject: Re: Network stack timer hacks for power saving
Date: Tue, 19 May 2009 11:04:08 +0200 [thread overview]
Message-ID: <4A127608.5020109@cosmosbay.com> (raw)
In-Reply-To: <1F18D6510CF0474A8C9500565A7E41A20544D923FF@NOK-EUMSG-02.mgdnok.nokia.com>
Tero.Kristo@nokia.com a écrit :
> Hi,
>
> I have been looking at network stack timer optimization for
> power saving in embedded ARM environment, basically trying to
> avoid as many wakeups as possible. I have changed several
> timers in the network stack into deferred ones, i.e. they do
> not wake up the device from low power modes but instead they
> are deferred until next wakeup from some other source, like
> another (non-deferred) timer or some I/O. Attached a patch
> about the changes I've done, is something like this safe to do?
>
> -Tero
Hi Tero
When tcp communications are active, we setup a timer for *every* frame
we receive or we send. These timers wont be deferrable anyway.
delaying one wakeup every 60 seconds (if I take your net/ipv4/route.c change)
wont change that much power savings, or did I missed something ?
On big routers, we need to set ip_rt_gc_interval from 60 seconds to one second,
in order to perform an effective garbage collection.
So, if we use a deferred timer and :
schedule_delayed_work(&expires_work, HZ);
How many times worker will be started every minute ?
next prev parent reply other threads:[~2009-05-19 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 8:13 Network stack timer hacks for power saving Tero.Kristo
2009-05-19 9:04 ` Eric Dumazet [this message]
2009-05-19 9:46 ` Tero.Kristo
2009-05-19 18:56 ` [PATCH] net: use a deferred timer in rt_check_expire Eric Dumazet
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=4A127608.5020109@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=Tero.Kristo@nokia.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).