From: Robert Hancock <hancockr@shaw.ca>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mikhail Kshevetskiy <mikhail.kshevetskiy@gmail.com>,
linux-kernel@vger.kernel.org, aabdulla@nvidia.com,
jgarzik@pobox.com
Subject: Re: forcedeth: option to disable 100Hz timer (try 2)
Date: Wed, 10 Sep 2008 18:18:20 -0600 [thread overview]
Message-ID: <48C863CC.3010902@shaw.ca> (raw)
In-Reply-To: <fa.4uZtuq0waBlpfBb/4OLq4bM5Pj8@ifi.uio.no>
Andrew Morton wrote:
> On Tue, 9 Sep 2008 23:34:35 +0400
> Mikhail Kshevetskiy <mikhail.kshevetskiy@gmail.com> wrote:
>
>> On some hardware no TX done interrupts are generated, thus special
>> 100Hz timer interrupt is required to handle this situation properly.
>> Other device do not require that timer interrupt feature.
>>
>> Forcedeth has a DEV_NEED_TIMERIRQ flag to mark the broken devices.
>> Unfortunately, nobody know the actual list of broken devices, so all
>> device has this flag on. Other problem, this flag is not user visible,
>> so the kernel recompilation is required to disable timer interrupts and
>> test a device.
>>
>> This patch add a "disable_timerirq" option to disable interrupt
>> timer mentioned above. This may be extremely useful for laptop users.
>
> Why do you feel that the timer-based completions need to be disabled?
> Is it causing some problem?
100 unnecessary CPU wakeups per second imposes some power usage cost,
especially on laptops with CPU C-states..
next parent reply other threads:[~2008-09-11 0:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.iCGOiwuSYhYKpu85Kihny1t9YbA@ifi.uio.no>
[not found] ` <fa.4uZtuq0waBlpfBb/4OLq4bM5Pj8@ifi.uio.no>
2008-09-11 0:18 ` Robert Hancock [this message]
2008-09-11 0:36 ` forcedeth: option to disable 100Hz timer (try 2) Andrew Morton
2008-09-11 4:19 ` Mikhail Kshevetskiy
2008-09-11 4:25 ` Robert Hancock
2008-09-11 5:19 ` Andrew Morton
2008-09-11 5:31 ` Mikhail Kshevetskiy
2008-09-11 19:14 ` Alan Cox
[not found] <baho5-34g-25@gated-at.bofh.it>
2008-09-10 11:16 ` Bodo Eggert
2008-09-09 19:34 Mikhail Kshevetskiy
2008-09-10 23:31 ` Andrew Morton
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=48C863CC.3010902@shaw.ca \
--to=hancockr@shaw.ca \
--cc=aabdulla@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.kshevetskiy@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.