aboutsummaryrefslogtreecommitdiff
path: root/drivers/net/phy/phy_device.c
diff options
context:
space:
mode:
authorArjan van de Ven <arjan@linux.intel.com>2007-03-06 02:41:48 -0800
committerJeff Garzik <jeff@garzik.org>2007-04-28 11:00:57 -0400
commit56e1393f82349d8206fe7feb94db96b065c55e51 (patch)
tree431010e7b3641b2589b7a7501b21ee15bbfdaf37 /drivers/net/phy/phy_device.c
parenteea221ce48803a92e2319270b2b7b8e21cd470ca (diff)
downloadlinux-linaro-android-56e1393f82349d8206fe7feb94db96b065c55e51.tar.gz
user of the jiffies rounding code: e1000
Use the round_jiffies() function in e1000. These timers all were of the "about once a second" or "about once every X seconds" variety and several showed up in the "what wakes the cpu up" profiles that the tickless patches provide. Some timers are highly dynamic based on network load; but even on low activity systems they still show up so the rounding is done only in cases of low activity, allowing higher frequency timers in the high activity case. The various hardware watchdogs are an obvious case; they run every 2 seconds but aren't otherwise specific of exactly when they need to run. Signed-off-by: Arjan van de Ven <arjan@linux.intel.com> Acked-by: Auke Kok <auke-jan.h.kok@intel.com> Cc: Jeff Garzik <jeff@garzik.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Jeff Garzik <jeff@garzik.org>
Diffstat (limited to 'drivers/net/phy/phy_device.c')
0 files changed, 0 insertions, 0 deletions