Linux wireless drivers development
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Zhu Yi <yi.zhu@intel.com>
Cc: linux-wireless@vger.kernel.org, ipw2100-devel@lists.sourceforge.net
Subject: Re: [PATCH] ipw2200: batch non-user-requested scan result notifications
Date: Mon, 22 Oct 2007 11:47:18 -0400	[thread overview]
Message-ID: <1193068039.30205.13.camel@localhost.localdomain> (raw)
In-Reply-To: <1193042719.3069.166.camel@debian.sh.intel.com>

On Mon, 2007-10-22 at 16:45 +0800, Zhu Yi wrote:
> On Tue, 2007-10-09 at 13:55 -0400, Dan Williams wrote:
> > ipw2200 makes extensive use of background scanning when unassociated
> > or
> > down.  Unfortunately, the firmware sends scan completed events many
> > times per second, which the driver pushes directly up to userspace.
> > This needlessly wakes up processes listening for wireless events many
> > times per second.  Batch together scan completed events for
> > non-user-requested scans and send them up to userspace every 4
> > seconds.
> > Scan completed events resulting from an SIOCSIWSCAN call are pushed up
> > without delay.
> > 
> > Signed-off-by: Dan Williams <dcbw@redhat.com>
> 
> I'm OK with this one except the round_jiffies part.

I think that it got fixed upstream when the round_jiffies_relative()
patch went it, is that what you mean?  If not, I'm not sure what you
mean by "except the round_jiffies part".

Dan

> Thanks,
> -yi
> -
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2007-10-22 15:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09 17:55 [PATCH] ipw2200: batch non-user-requested scan result notifications Dan Williams
2007-10-22  8:45 ` Zhu Yi
2007-10-22 15:47   ` Dan Williams [this message]
2007-10-23  0:58     ` Zhu Yi

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=1193068039.30205.13.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=ipw2100-devel@lists.sourceforge.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=yi.zhu@intel.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