From: David Miller <davem@davemloft.net>
To: dada1@cosmosbay.com
Cc: shemminger@linux-foundation.org, parag.warudkar@gmail.com,
netdev@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH 2/2] net: neighbor timer power saving
Date: Thu, 20 Dec 2007 15:28:56 -0800 (PST) [thread overview]
Message-ID: <20071220.152856.39725559.davem@davemloft.net> (raw)
In-Reply-To: <4768C6FF.2090909@cosmosbay.com>
From: Eric Dumazet <dada1@cosmosbay.com>
Date: Wed, 19 Dec 2007 08:23:43 +0100
> We are going to convert 99% timers to deferrable.
>
> Maybe the right move should be to have the reverse attribute, to
> mark a timer as non deferrable...
I think we are still in a learning process about what
exactly causes a timer to be converted to deferrable
or not.
It may sound crazy but flipping the switch on %99 of
our kernel timers is not the nicest way to figure it
out :-)
Therefore it might still make sense to keep the deferrable
marker for now, so that we can gradually convert the tree
checking easy case carefully. This way the breakage is
containted very well.
Then once we have almost all of the timers verified, we
can reverse the meaning and mark the timers that remain
as non-deferrable and kill the deferrable marker.
prev parent reply other threads:[~2007-12-20 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 1:04 [PATCH] sch_generic.c: Make dev_watchdog use deferrable timer Parag Warudkar
2007-12-19 2:18 ` [PATCH 1/2] net: flow hash timer power saving Stephen Hemminger
[not found] ` <20071218174120.4b0ef6dd@shemminger-laptop>
2007-12-19 2:18 ` [PATCH 2/2] net: neighbor " Stephen Hemminger
2007-12-19 7:23 ` Eric Dumazet
2007-12-20 17:10 ` Stephen Hemminger
2007-12-20 18:16 ` Parag Warudkar
2007-12-20 23:28 ` David Miller [this message]
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=20071220.152856.39725559.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=dada1@cosmosbay.com \
--cc=netdev@vger.kernel.org \
--cc=parag.warudkar@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).