linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [mac80211/ath9k] mac80211/ath9k:  Support AMPDU with multiple VIFs.
Date: Tue, 21 Sep 2010 12:17:02 -0700	[thread overview]
Message-ID: <4C9904AE.7060107@candelatech.com> (raw)
In-Reply-To: <1285096048.12764.9.camel@jlt3.sipsolutions.net>

On 09/21/2010 12:07 PM, Johannes Berg wrote:
> On Tue, 2010-09-21 at 11:57 -0700, greearb@candelatech.com wrote:
>> From: Ben Greear<greearb@candelatech.com>
>>
>> The old ieee80211_find_sta_by_hw method didn't properly
>> find VIFS when there was more than on per AP.  This caused
>> AMPDU logic in ath9k to get the wrong VIF when trying to
>> account for transmitted SKBs.
>>
>> This patch changes ieee80211_find_sta_by_hw to take a
>> net_device pointer to distinguish among multiple VIFs.
>
> Err, no, this certainly isn't the right thing to do, is skb->dev even
> guaranteed to be right? I'm not convinced of that, and besides, if you
> can have the dev you can have the vif too.

The tx path doesn't seem to pass in more than the hardware and the skb,
and we don't always need to lookup the VIF, so looking it up early is
probably a waste.

mac80211 could be changed to pass in the VIF in the xmit path,
and then we could make sure that is passed through the entire
xmit process, but that would touch a lot of drivers and code.

The skb->dev appears to be valid.  Even if the device goes away, we are not
de-referencing the skb->dev anywhere, so it should still be OK.

I can't think of any good reason to corrupt the skb->dev within the xmit
logic, but this is all inside of ath9k anyway, so we should have full
control over that.

I have tested this, and it works.  I don't claim it's the best, but
it may easily be better than what currently exists.

I'm more than happy to test any patches if someone thinks up
a different approach.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2010-09-21 19:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21 18:57 [mac80211/ath9k] mac80211/ath9k: Support AMPDU with multiple VIFs greearb
2010-09-21 19:07 ` Johannes Berg
2010-09-21 19:17   ` Ben Greear [this message]
2010-09-21 19:19     ` Johannes Berg
2010-09-21 19:29       ` Ben Greear

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=4C9904AE.7060107@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --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).