From: Johannes Berg <johannes@sipsolutions.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: tell driver when idle
Date: Wed, 29 Apr 2009 16:39:59 +0200 [thread overview]
Message-ID: <1241015999.593.62.camel@johannes.local> (raw)
In-Reply-To: <1241015587.997.76.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
Hi Marcel,
> > Is it appropriate to go into idle state for a short time when we have
> > just authenticated, but not associated yet? This happens only with the
> > userspace SME, because we cannot really know how long it will wait
> > before asking us to associate. Would going idle after a short timeout
> > be more appropriate? We may need to revisit this, depending on what
> > happens.
>
> what about having the hardware set a value for how long something should
> be idle before you tell it. I am more thinking about some sort penalty
> value from the hardware that can not do this quickly.
You're only referring to this case of between auth/assoc, right? I'm not
sure it makes sense to have this HW dependent, the time between
auth/assoc really only depend on how fast the SME is. If we first wait a
bit, because HW advertises some "penalty value", and then the SME is
just a little bit slower than that value, we'd get an even worse
situation, no?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-04-29 14:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 9:32 [PATCH] mac80211: tell driver when idle Johannes Berg
2009-04-29 9:51 ` Johannes Berg
2009-04-29 10:26 ` [PATCH v2] " Johannes Berg
2009-04-29 14:33 ` [PATCH] " Marcel Holtmann
2009-04-29 14:39 ` Johannes Berg [this message]
2009-04-29 15:14 ` Marcel Holtmann
2009-04-29 16:11 ` Johannes Berg
2009-04-29 16:20 ` Marcel Holtmann
2009-04-29 16:28 ` Johannes Berg
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=1241015999.593.62.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=marcel@holtmann.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 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.