linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Vivek Natarajan <Vivek.Natarajan@Atheros.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: RE: multicast traffic and ath9k
Date: Fri, 09 Jan 2009 14:07:26 +0100	[thread overview]
Message-ID: <1231506446.3703.18.camel@johannes> (raw)
In-Reply-To: <44EE5C37ADC36343B0625A05DD408C4845A77DAF07@CHEXMB-01.global.atheros.com>

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

On Fri, 2009-01-09 at 18:26 +0530, Vivek Natarajan wrote:
> Johannes Berg wrote:
> 
> > I'm inclined to ask you to remove that multicast checking from mac80211
> > and do it closer to the hardware, and simply require from the
> > driver/hardware that mac80211 needs not do anything for multicast
> > traffic. Mostly because I'm thinking that once we start relying on the
> > software implementation in mac80211 the delay may be too large.
> 
> I'm curious to know how this is implemented in other vendor drivers because
> beacon processing is shared between the hw and sw. mc bit is processed in
> the hw whereas tim bit and timestamp update need sw's help.

That seems to be the case at least for p54 (stlc45xx). Not really sure
about others.

> Is the mc bit
> checking done only on enabling power save? if set and mc packets are received,
> how does it automatically go back to sleep and wouldn't there be any conflict
> between mac80211 and the hw regarding power state since mac80211 is not aware
> of the mc bit induced state change?

I don't think there would be a conflict. mac80211's CONF_PS is always
only "go to sleep if you can", so receiving multicast traffic would
obviously imply not being able to go to sleep. When mac80211 then unsets
the CONF_PS flag you'd just not go back to sleep after being awake for
MC traffic.

johannes

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

  reply	other threads:[~2009-01-09 13:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 16:36 multicast traffic and ath9k Johannes Berg
2009-01-09 11:50 ` Vivek Natarajan
2009-01-09 11:57   ` Johannes Berg
2009-01-09 12:56 ` Vivek Natarajan
2009-01-09 13:07   ` Johannes Berg [this message]
2009-01-09 13:59     ` Vivek Natarajan
2009-01-09 16:13       ` Christian Lamparter
2009-01-09 17:33         ` Kalle Valo
2009-01-09 16:37       ` Kalle Valo

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=1231506446.3703.18.camel@johannes \
    --to=johannes@sipsolutions.net \
    --cc=Vivek.Natarajan@Atheros.com \
    --cc=linux-wireless@vger.kernel.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 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).