linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Jiri Benc <jbenc@suse.cz>, jketreno <jketreno@linux.intel.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Michael Wu <flamingice@sourmilk.net>
Subject: Re: Specifing rate control algorithm?
Date: Thu, 10 May 2007 20:12:12 -0400	[thread overview]
Message-ID: <20070511001212.GB6971@tuxdriver.com> (raw)
In-Reply-To: <1ba2fa240705101524x2676a09eyeff3b71ed2542478@mail.gmail.com>

On Fri, May 11, 2007 at 01:24:58AM +0300, Tomas Winkler wrote:
> On 5/10/07, Jiri Benc <jbenc@suse.cz> wrote:
> >On Thu, 10 May 2007 13:17:12 -0700, jketreno wrote:

> >> Generic algorithms aren't as capable as hardware specific algorithms
> >> when you factor performance, latency, system utilization, power
> >> consumption, etc.  Optimal algorithms are written to take advantage of
> >> the capabilities exposed by the hardware.
> >
> >You said the same about hardware scanning. Michael showed you that's
> >not true.
> >
> Michael has shortened the dwell time on the channel, while hw scanning
> has shorten switching time from the channel to channel and no the time
> you are listening on the channel
> I wouldn't call it an optimization. Did he measured the power consumption ?

This was going to be my question, and I think it is a worthy point. :-)

John

> >If the slowdown is not big, yes, it is. Unifying things almost always
> >means you need to accept some trade-offs.
> 
> Clean API gives you the ability to enjoy from the both worlds. WiFi is
> about mobility power saving and therefore hw offloading is essential.
> What worth the few more lines of the code that gives you this ability
> this is also a trade-off.

Agreed.  FWIW, power saving is worthwhile even for fixed stations as well.

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2007-05-11  0:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09 23:05 Specifing rate control algorithm? James Ketrenos
2007-05-10 11:27 ` Jiri Benc
2007-05-10 15:48   ` Jouni Malinen
2007-05-10 16:00     ` Tomas Winkler
2007-05-10 16:17   ` James Ketrenos
2007-05-10 17:11     ` Johannes Berg
2007-05-10 17:26       ` Jouni Malinen
2007-05-10 19:36       ` jketreno
2007-05-11 11:36         ` Johannes Berg
2007-05-10 17:42     ` Jiri Benc
2007-05-10 20:17       ` jketreno
2007-05-10 19:23         ` Jiri Benc
2007-05-10 22:24           ` Tomas Winkler
2007-05-11  0:12             ` John W. Linville [this message]
2007-05-11  8:09               ` Andy Green
2007-05-11  9:07                 ` Jeff Garzik
2007-05-11  9:36                   ` Andy Green
2007-05-11 14:23                 ` Jouni Malinen
2007-05-11 15:04                   ` Andy Green
2007-05-11 15:42                     ` Jouni Malinen
2007-05-11 10:21             ` Jiri Benc

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=20070511001212.GB6971@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=flamingice@sourmilk.net \
    --cc=jbenc@suse.cz \
    --cc=jketreno@linux.intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tomasw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).