From: "Parag Warudkar" <parag.warudkar@gmail.com>
To: "Stephen Hemminger" <shemminger@linux-foundation.org>
Cc: "Eric Dumazet" <dada1@cosmosbay.com>,
linux-kernel@vger.kernel.org,
"David Miller" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: init_timer_deferrable conversion
Date: Mon, 17 Dec 2007 12:47:59 -0500 [thread overview]
Message-ID: <82e4877d0712170947v45929acv92e0d34c86d82c6d@mail.gmail.com> (raw)
In-Reply-To: <20071217090000.64499fba@deepthought>
On Dec 17, 2007 12:00 PM, Stephen Hemminger
<shemminger@linux-foundation.org> wrote:
> > > >
> > > > a) drivers/net/sky2.c - watchdog_timer. This was showing up high on
> > > > Powertop's list of things that cause routine wakeups from idle. After
> > > > converting to init_timer_deferrable() the wakeups went down and this one
> > > > no longer shows up in powertop's list. 25% reduction.
>
> This surprises me because it is a 1 hz timer and uses round_jiffies() in
> the current kernel.
I am using the current git and I already have low wakeups per second
to begin with - 5-7 and out of that 25% are attributed to sky2. Not
sure if that matches up with the 1 hz + round_jiffies() logic.
But is it conceptually ok to make this deferrable? I suppose yes as
it's just a watchdog that checks if the link is up and delaying that
would not make a difference?
Thanks
Parag
next prev parent reply other threads:[~2007-12-17 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 3:00 Parag Warudkar
2007-12-17 8:55 ` Eric Dumazet
2007-12-17 14:29 ` Eric Dumazet
2007-12-17 17:00 ` Stephen Hemminger
2007-12-17 17:47 ` Parag Warudkar [this message]
2007-12-18 6:09 ` Parag Warudkar
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=82e4877d0712170947v45929acv92e0d34c86d82c6d@mail.gmail.com \
--to=parag.warudkar@gmail.com \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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
all inboxes | Powered by JetHome®