Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Tomas Winkler" <tomasw@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
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 13:33:22 +0200	[thread overview]
Message-ID: <1ba2fa240802250333p1d0a4ebqd37ff4f837aa556f@mail.gmail.com> (raw)
In-Reply-To: <1203937235.13162.83.camel@johannes.berg>

On Mon, Feb 25, 2008 at 1:00 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> > > >  > 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?

I would notify mac only if driver cannot deal with reset and also
mac80211 configuration have to be reapplied such as start association
process again in STA mode.   It would be probably security problem if
we put just station into associated mode without proper association
process.
If in AP mode  stations have only soft state that it would be probably
not necessary to reset station table.

Tomas

>  johannes
>

  reply	other threads:[~2008-02-25 11:33 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
2008-02-25 11:33           ` Tomas Winkler [this message]
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=1ba2fa240802250333p1d0a4ebqd37ff4f837aa556f@mail.gmail.com \
    --to=tomasw@gmail.com \
    --cc=br1@einfach.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@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