From: Alexey.Brodkin@synopsys.com (Alexey Brodkin)
To: linux-snps-arc@lists.infradead.org
Subject: rsi_91x: Low bandwidth: sends ~100 Kbits/sec, receives ~1.5 Mbits/sec
Date: Fri, 15 Dec 2017 11:20:41 +0000 [thread overview]
Message-ID: <1513336840.29404.21.camel@synopsys.com> (raw)
In-Reply-To: <b4c2093d-cc2c-cdd3-52a5-73cefd2c189a@redpinesignals.com>
Hi Prameela,
On Fri, 2017-12-15@11:13 +0530, Prameela Rani Garnepudi wrote:
> Hi Alexey,
>
> Please use the attached patch to improve TX throughput. We will be
> submitting this patch along with few others soon.
Could you please specify which branch this patch is based on?
I tried to apply on 4.14.5 (whatever is latests in "linux-4.14.y")
but first 3 hunks failed to apply.
Maybe there're other dependencies?
Also a couple of questions about this patch.
Even though I'm not a networking/Wi-Fi expert of any kind but just
looking at your changes:
1. I assume for upstreaming that patch will be split in 5 seperate patches
each addressing its own item instead of doing all at once, right?
2. The only obvious change that might help me with bandwidth is increase
of a number of aggregated Tx frames. But bumping from 6 to 8 doesn't look
as a significant improvement. How that might bring Tx bandwidth at least to
what I see on Rx, i.e. make things 10 times faster?
Also while at it I'm wondering why 5GHz mode didn't work for me even though
"iw list" reports 5 GHz mode supported:
----------------------->8------------------
# iw list
Wiphy phy0
...
Frequencies:
* 5180 MHz [36] (20.0 dBm) (no IR)
# cat /etc/hostapd.conf
interface=wlan0
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
ssid=HSDK-AP
hw_mode=a
channel=36
# hostapd -B /etc/hostapd.conf
Starting hostapd: Configuration file: /etc/hostapd.conf
rsi_91x: ===> Interface UP <===
rfkill: Cannot open RFKILL contrIPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
ol device
wlan0: IEEE 802.11 Configured channel (36) not found from the channel list of current mode (2) IEEE 802.11a
wlan0: IEEE 802.11 Hardware does not support configured channel
Could not select hw_mode and channel. (-3)
wlan0: interface state UNINITIALIZED->DISABLED
wlan0: AP-DISABLED
wlan0: Unable to setup interface.
wlan0: interface state DISABLED->DISABLED
wlan0: AP-DISABLED
hostapd_free_hapd_data: Interface wlan0 wasn't started
----------------------->8------------------
Has it something to do with your another fix in that patch?
-Alexey
next prev parent reply other threads:[~2017-12-15 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 16:11 rsi_91x: Failed to read status register on failed authentication Alexey Brodkin
2017-12-06 7:13 ` Amitkumar Karwar
2017-12-14 18:56 ` rsi_91x: Low bandwidth: sends ~100 Kbits/sec, receives ~1.5 Mbits/sec Alexey Brodkin
[not found] ` <b4c2093d-cc2c-cdd3-52a5-73cefd2c189a@redpinesignals.com>
2017-12-15 11:20 ` Alexey Brodkin [this message]
[not found] ` <3f553fb0-d1d2-59f1-32f3-53e993c544ca@redpinesignals.com>
2017-12-15 13:21 ` Alexey Brodkin
2017-12-15 16:09 ` rsi_91x: Failed to read status register on failed authentication Alexey Brodkin
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=1513336840.29404.21.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=linux-snps-arc@lists.infradead.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).