From: Yaroslav Isakov <yaroslav.isakov@gmail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: ath11k@lists.infradead.org
Subject: Re: wcn6855 - stuck in 20Mhz on rx, but full 80mhz on tx
Date: Fri, 29 Dec 2023 18:38:50 +0100 [thread overview]
Message-ID: <CADS+iDV276z5CHcnPVf5A0dUZtKStW6M1zEe6H44nOz0hn6crg@mail.gmail.com> (raw)
In-Reply-To: <c5d1124b-ad4a-b5f0-db29-7050f1f04bb1@candelatech.com>
пт, 29 дек. 2023 г. в 18:20, Ben Greear <greearb@candelatech.com>:
>
> On 12/29/23 9:06 AM, Yaroslav Isakov wrote:
> > пт, 29 дек. 2023 г. в 17:46, Yaroslav Isakov <yaroslav.isakov@gmail.com>:
> >>
> >> Hello! I managed to get another router, Asus TUF-AX6000 (with openwrt,
> >> too), and on this one, there is the same problem with rx
> >> bitrate/channel width display, in AC mode.
> >
> > Looks like the issue was with GCMP-256 cipher. I changed all ciphers
> > to the AC ones (CCMP+BIP), and now upload and download speeds are
> > around 1gigabit. I'll try different ones, to see if there is issue
> > with only one, or with all modern ciphers.
> >
>
> The linux kernel's software decrypt performs poorly, partially due to
> the crypto folks' refusal to add in the aesni crypto accelerator logic.
>
> Thanks,
> Ben
>
> --
> Ben Greear <greearb@candelatech.com>
> Candela Technologies Inc http://www.candelatech.com
>
I thought, all such ciphers are implemented in hardware? I tried to
load ath11k with crypto_mode=1, to see, if it will make any difference
- and yes, it made - download speed becomes even lower.
I've tried different pairwise_cipher options, and the only one giving
me expected speed was CCMP (not even CCMP-256). mgmt_group_cipher
makes no difference, so, I can set BIP-GMAC-256, and if
pairwise_cipher is CCMP, I'm getting 1+ gbit.
prev parent reply other threads:[~2023-12-29 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 18:15 wcn6855 - stuck in 20Mhz on rx, but full 80mhz on tx Yaroslav Isakov
2023-12-13 5:16 ` Kalle Valo
2023-12-13 18:57 ` Yaroslav Isakov
2023-12-14 15:11 ` Kalle Valo
2023-12-14 20:29 ` Yaroslav Isakov
2023-12-27 9:32 ` Yaroslav Isakov
2023-12-29 16:46 ` Yaroslav Isakov
2023-12-29 17:06 ` Yaroslav Isakov
2023-12-29 17:19 ` Ben Greear
2023-12-29 17:38 ` Yaroslav Isakov [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=CADS+iDV276z5CHcnPVf5A0dUZtKStW6M1zEe6H44nOz0hn6crg@mail.gmail.com \
--to=yaroslav.isakov@gmail.com \
--cc=ath11k@lists.infradead.org \
--cc=greearb@candelatech.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).