public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Johannes Berg <johannes@sipsolutions.net>
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 09:20:06 -0700	[thread overview]
Message-ID: <1241022006.4104.6.camel@localhost.localdomain> (raw)
In-Reply-To: <1241021479.22715.6.camel@johannes.local>

Hi Johannes,

> > there can be always a situation where this ends up badly. You tell the
> > hardware that it can sleep now, but then you change your mind because
> > userspace finally got its act together. Bad luck.
> 
> Right.
> 
> > My point here is only that if the hardware needs a certain amount of
> > time before it makes sense to sleep, it should just tell mac80211 this
> > and it should be honored.
> 
> I don't really see how that makes sense though. Why would the hardware
> "need[] a certain amount of time before it makes sense to sleep"? How
> would it not make sense to go to sleep whenever possible, right away,
> however long the hardware needs to actually go to sleep then?
> 
> Yes, it's possible that the hardware takes a little while to wake up
> again, but we can only account for that if we can predict when we need
> to wake up again in the future, but we definitely can't. So yes, while
> it doesn't make sense to tell the hw we're idle when we will only be
> idle for 50ms and the hw needs 30 to go into idle and 30 to get out of
> it, I'm not sure how telling it that it needs 30ms will help mac80211.
> Going to idle and coming out of it is meant to be synchronous, so
> mac80211 will always wait for the driver to finish that operation.
> 
> > The default should be that we try how good the hardware can handle
> > mac80211 being aggressive with switching to idle. Maybe auth/assoc is a
> > special case anyway and we should have a sensible timeout value. We
> > could ask userspace to tell use that value when doing auth, but that
> > feels kinda ugly to me.
> 
> Being idle between auth and assoc probably is a special case, yeah. So
> far iwlwifi has handled it just fine for me though, so I'm inclined to
> not worry about it too much. Well, with the race fix...

I am all for just trying and then actually see if hardware falls over,
because we are too aggressive. However you asked about it in the first
place, and got my comment ;)

Regards

Marcel



  reply	other threads:[~2009-04-29 16:20 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
2009-04-29 15:14     ` Marcel Holtmann
2009-04-29 16:11       ` Johannes Berg
2009-04-29 16:20         ` Marcel Holtmann [this message]
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=1241022006.4104.6.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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