From: Marlon Smith <marlon.smith10@gmail.com>
To: Jean-Pierre TOSONI <jp.tosoni@acksys.fr>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Strange performance issue when using two devices at once
Date: Thu, 30 Jan 2020 10:26:46 -0500 [thread overview]
Message-ID: <1580398006.26012.81.camel@gmail.com> (raw)
In-Reply-To: <AM0PR01MB43879C1D5C9FF8744B5ADDD1E4040@AM0PR01MB4387.eurprd01.prod.exchangelabs.com>
On Thu, 2020-01-30 at 14:55 +0000, Jean-Pierre TOSONI wrote:
> Maybe you need to put some distance between the 3 devices.
> We experienced this kind of problem on radios close to each other
> (around 10cm).
> It was due to radio signals inducing themselves in the PCB of another
> nearby radio, causing the other radio to badly transmit and receive.
>
> >
> > -----Message d'origine-----
> > De : linux-wireless-owner@vger.kernel.org [mailto:linux-wireless-ow
> > ner@vger.kernel.org] De la part de
> > Marlon Smith
> > Envoyé : mercredi 29 janvier 2020 19:40
> > À : linux-wireless@vger.kernel.org
> > Objet : Strange performance issue when using two devices at once
> >
> > Hi everyone,
> >
> > I have two RT5370 devices connected to the same access point. Both
> > devices are very slow, but the instant I disconnect one device, the
> > other speeds up by a factor of 10.
> >
> > The really strange part is that one device will perform slowly even
> > if
> > the other device is basically idle! I've confirmed this with a
> > packet
> > sniffer.
> >
> > I've been trying to do some debugging, and I've found that when
> > both
> > devices are connected to the access point, they report a large
> > number
> > of duplicate frames. I added some debug output
> > in ieee80211_rx_h_check_dup() to confirm that this only happens
> > while
> > both devices are connected. The packet sniffer also shows a large
> > number of retries while this is occurring.
> >
> > Using backports 5.3-rc4 for this, but also tested on 4.14-rc2.
> >
> > I did post about this previously on this mailing list (RT5370
> > performance issues), but I thought I'd post again with this new
> > information and more descriptive title. I'm a little bit stuck on
> > this
> > for a while now, so any ideas are much appreciated.
> >
> > Thanks!
> >
> > Marlon
Thanks for the reply Jean-Pierre. I just discovered this morning that
if I change the MAC address of one of the devices, they both perform
well. So I'm wondering if it is a driver issue.
However I will keep this in mind, as I often do have multiple devices
together in close proximity.
prev parent reply other threads:[~2020-01-30 15:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 18:39 Strange performance issue when using two devices at once Marlon Smith
2020-01-29 18:42 ` Ben Greear
2020-01-29 19:22 ` Marlon Smith
2020-01-29 19:27 ` Ben Greear
2020-01-29 19:48 ` Marlon Smith
2020-01-29 20:01 ` Ben Greear
2020-01-29 20:49 ` Marlon Smith
2020-01-30 14:43 ` Marlon Smith
2020-01-30 15:32 ` Felix Fietkau
2020-01-30 16:04 ` Marlon Smith
2020-01-30 14:55 ` Jean-Pierre TOSONI
2020-01-30 15:26 ` Marlon Smith [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=1580398006.26012.81.camel@gmail.com \
--to=marlon.smith10@gmail.com \
--cc=jp.tosoni@acksys.fr \
--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).