Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Tomas Winkler <tomasw@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	bruno randolf <br1@einfach.org>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>
Subject: Re: mac80211 locking: tasklet vs. non-tasklet
Date: Mon, 25 Feb 2008 12:00:35 +0100	[thread overview]
Message-ID: <1203937235.13162.83.camel@johannes.berg> (raw)
In-Reply-To: <1203937042.13162.81.camel@johannes.berg> (sfid-20080225_105732_203616_A9BE06D8)

[-- Attachment #1: Type: text/plain, Size: 730 bytes --]

> > >  > A disconnection can happen due to
> > >  > device resume or internal recoverable error. In this cases I would
> > >  > expect mac to try associate again upon such trigger.
> > >
> > >  I guess that's just missing. You can stop the queues but you can't tell
> > >  mac80211 that you reset the hw.
> > 
> > If there is no objection we will introduce some notification
> > mechanism...suggestions are welcome as well.
> 
> I have no objection, though I'm unsure what precisely you want. What,
> for example, if you're running hostapd and your hardware resets? Can you
> keep station tables etc.?

I mean, if the hw simply resets quickly then I would expect the
association to withstand that, no?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2008-02-25 11:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22 10:29 mac80211 locking: tasklet vs. non-tasklet Johannes Berg
2008-02-24 16:29 ` Tomas Winkler
2008-02-25  9:51   ` Johannes Berg
2008-02-25 10:52     ` Tomas Winkler
2008-02-25 10:57       ` Johannes Berg
2008-02-25 11:00         ` Johannes Berg [this message]
2008-02-25 11:33           ` Tomas Winkler
2008-02-25 11:36             ` 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=1203937235.13162.83.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=br1@einfach.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --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