public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mikhail Kshevetskiy <mikhail.kshevetskiy@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Robert Hancock <hancockr@shaw.ca>,
	linux-kernel@vger.kernel.org, aabdulla@nvidia.com,
	jgarzik@pobox.com
Subject: Re: forcedeth: option to disable 100Hz timer (try 2)
Date: Thu, 11 Sep 2008 09:31:09 +0400	[thread overview]
Message-ID: <20080911093109.2cc34135@laska> (raw)
In-Reply-To: <20080910221947.94409642.akpm@linux-foundation.org>

On Wed, 10 Sep 2008 22:19:47 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:

> On Wed, 10 Sep 2008 22:25:03 -0600 Robert Hancock <hancockr@shaw.ca> wrote:
> 
> > Enabling by 
> > default and disabling after a TX done interrupt was received would 
> > likely be a better approach
> 
> yup, that's far better.

How it will work, if network cable unpluged? This is quite often situation
for laptop with wifi?

> 
> > But it's quite likely that at least some of the 
> > chipsets that this driver supports don't need this timer nonsense at all
> 
> Well yes.  If all the chipsets need the timer then there's nothing we
> can do to improve it.
> 

  reply	other threads:[~2008-09-11  5:38 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   ` forcedeth: option to disable 100Hz timer (try 2) Robert Hancock
2008-09-11  0:36     ` 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 [this message]
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=20080911093109.2cc34135@laska \
    --to=mikhail.kshevetskiy@gmail.com \
    --cc=aabdulla@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=hancockr@shaw.ca \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.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