From: Arjan van de Ven <arjan@linux.intel.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Larry Finger <larry.finger@lwfinger.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: round_jiffies for schedule_delayed_work?
Date: Thu, 15 Feb 2007 19:16:29 +0100 [thread overview]
Message-ID: <45D4A37D.8000203@linux.intel.com> (raw)
In-Reply-To: <20070215150615.GB3310@tuxdriver.com>
John W. Linville wrote:
> On Wed, Feb 14, 2007 at 10:39:23PM +0100, Johannes Berg wrote:
>> Hi,
>>
>> I was looking through recent commits in wireless-dev and found
>> e226b8aa8921b6b75dcd0142a990b8c7bc1548fd which is correct, but I was
>> wondering if it may be possible to do it more efficiently.
>>
>> We don't really need this code running every second after we init,
>> having it run every second on average is good enough. I don't see any
>> way to do this with the delayed work API though since
>> schedule_delayed_work simply adds the timer at jiffies+delay.
>>
>> Should we be using a timer and round_jiffies() instead?
>
> Using round_jiffies seems reasonable. Perhaps the delayed work API
> can be extended to use it?
there is round_jiffies_relative() you can use for this kind of purpose....
next prev parent reply other threads:[~2007-02-15 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 21:39 round_jiffies for schedule_delayed_work? Johannes Berg
2007-02-15 15:06 ` John W. Linville
2007-02-15 18:16 ` Arjan van de Ven [this message]
2007-02-16 9:03 ` Johannes Berg
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=45D4A37D.8000203@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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