From: Ben Greear <greearb@candelatech.com>
To: Yu-Chieh <jay0607@gmail.com>, ath10k@lists.infradead.org
Subject: Re: Specific MAC address impact performance
Date: Mon, 26 Oct 2015 08:12:11 -0700 [thread overview]
Message-ID: <562E42CB.4090809@candelatech.com> (raw)
In-Reply-To: <CAGJdtRAxPKvNZAZK=YMTGd0mJKP=e2gatyofPz-1KpPj_kU5Rw@mail.gmail.com>
Your probably have BSSID mask collision. Rule of thumb is to leave
all octets the same except the second and third (from the right)
byte. That usually gives you unique masks assuming the right-most
byte is unique for your radios.
Thanks,
Ben
On 10/26/2015 03:50 AM, Yu-Chieh wrote:
> Hi,
>
> I am working on IBSS mode by using ath10k. However i met some problem
> about the performance issue
> First of all, i set up two nodes, A (74:DA:38:19:19:DC) and B
> (74:DA:38:06:E1:96) and run iperf.
> i can get around 170 Mbps form A to B
>
> Then, i turn on the third node C(74:DA:38:06:E1:BE).
> The performance is deteriorated to around 30Mbps.
> If i turn off node C, the performance go back to 170 Mbps.
>
> At the same environment and same devices, i jsut change the mac of B
> to (74:DA:38:06:E1:B2)
> Everything is good.
> No matter node c is on or off, the performance always keep on 170Mbps.
>
> Anyone have any idea about this problem?
>
> Jay
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
>
--
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
next prev parent reply other threads:[~2015-10-26 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 10:50 Specific MAC address impact performance Yu-Chieh
2015-10-26 15:12 ` Ben Greear [this message]
2015-10-26 17:38 ` Yu-Chieh
2015-10-26 17:47 ` Ben Greear
2015-10-27 15:51 ` Yu-Chieh
2015-10-27 16:12 ` Ben Greear
2015-10-27 16:34 ` Yu-Chieh
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=562E42CB.4090809@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=jay0607@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 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.