From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: Fix skb-copy failure debug message.
Date: Sun, 09 Jan 2011 09:45:14 -0800 [thread overview]
Message-ID: <4D29F42A.1040300@candelatech.com> (raw)
In-Reply-To: <1294565540.3469.0.camel@jlt3.sipsolutions.net>
On 01/09/2011 01:32 AM, Johannes Berg wrote:
> On Sat, 2011-01-08 at 10:30 -0800, greearb@candelatech.com wrote:
>> From: Ben Greear<greearb@candelatech.com>
>>
>> This particular error isn't about multicast.
>
> Actually, it is... only multicast frames should ever be processed by
> multiple interfaces.
Or if the STA interfaces are promisc for some reason..but no big
deal either way. With the old ath9k code, even arps or dhcp requests
would be an order-1 SKB, so that is probably what I was seeing.
I had a clean overnight run with the ath9k copybreak logic, so
that seems to have been the root problem.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2011-01-09 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 18:30 [PATCH] mac80211: Fix skb-copy failure debug message greearb
2011-01-09 9:32 ` Johannes Berg
2011-01-09 17:45 ` Ben Greear [this message]
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=4D29F42A.1040300@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).