From: Ben Greear <greearb@candelatech.com>
To: Vu Hai NGUYEN <vh.nguyen@actiasodielec.fr>
Cc: Patrick CARNEIRO RODRIGUEZ <p.carneiro@actiasodielec.fr>,
Michal Kazior <michal.kazior@tieto.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: RE : [PATCH] ath10k: fix aggregated 4addr Rx
Date: Thu, 31 Jul 2014 10:22:02 -0700 [thread overview]
Message-ID: <53DA7B3A.7000403@candelatech.com> (raw)
In-Reply-To: <EE97821C81277E459BEA5C6384C6F241012F15C1D805@srvexch01.SODIELEC.local>
On 07/31/2014 08:49 AM, Vu Hai NGUYEN wrote:
> Thank you for the patch. I applied it (manually not automatically, the patch is not based on ath-master branch?)
> The warning msg: br0: received packet on wlan0.sta1 with own address as source address disappeared on the console of my AP.
> But the performance of my bridged STA (using CT firmware) is still lower than non-bridged STA (10.1-467 firmware).
> (520 vs 550 Mbps)
>
> The processor of my AP is not exhausted (about 15-20% idle) but perf top on my bridged STA show that there is this thread: br_fdb_update.
> I didn't see it on non-bridged STA, it takes 5% resource of the processor
> I look for it on google and this thread is related to the warning message br0:received packet on wlan0.sta1 with own address as source address
> Do you guy have any suggestion?
Is there any way at all to make the standard firmware do bridged mode? I am curious if
the slow-down is due to my firmware or to bridging in general...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2014-07-31 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 12:36 [PATCH] ath10k: fix aggregated 4addr Rx Michal Kazior
2014-07-24 12:36 ` Michal Kazior
2014-07-29 9:44 ` Kalle Valo
2014-07-29 9:44 ` Kalle Valo
2014-07-31 15:49 ` RE : " Vu Hai NGUYEN
2014-07-31 17:22 ` 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=53DA7B3A.7000403@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=michal.kazior@tieto.com \
--cc=p.carneiro@actiasodielec.fr \
--cc=vh.nguyen@actiasodielec.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.