All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Eric Park <me@ericswpark.com>
Cc: ath10k@lists.infradead.org
Subject: Re: QCA6174 showing terrible performance when connecting via WPA3-SAE
Date: Thu, 25 Apr 2024 12:51:15 +0300	[thread overview]
Message-ID: <87wmolsrcc.fsf@kernel.org> (raw)
In-Reply-To: <a1231edb5e12283f6f5fbbf9e0ba7af8@ericswpark.com> (Eric Park's message of "Thu, 21 Mar 2024 05:05:34 +0100")

Eric Park <me@ericswpark.com> writes:

> Resending as I forgot to CC the mailing list, sorry! I've added some
> more info since the last email.

Thanks. Let's keep the discussion on the list so that others can join.

> On 2024-03-11 11:21, Kalle Valo wrote:
>> But with modern CPUs I would have still expected software encryption to
>> be faster than 20 Mbps so the chances are it can be something else as
>> well.
>
> I just checked and the laptop has an i5-5200U, but I'm not sure if
> it's the bottleneck. I ran a speedtest while monitoring the load and
> the CPU usage never went past 20-50% or so.

This depends how you measured CPU usage so I would not make any
conclusions from this yet. I also don't know what's the best way to
measure CPU usage from kernel driver point of view.

>> That's a user space decision and depends on what connection manager you
>> use.
>
> That's the weird part, for some reason I can't get it to force-connect
> via WPA2-PSK. I've tried KDE's network configuration and `nmtui`, but
> when I connect to the network it seems like it tries to negotiate with
> WPA2-PSK first and then "upgrades" to WPA3-SAE. Or at least that's how
> it appears in the network details dropdown if I click on the chevron
> next to the Wi-Fi SSID.

I do not use Network Manager or other connection managers when testing.
It's much more reliable to use wpasupplicant directly and you get full
control. I usually create a custom config file and then start the
supplicant manually. Some pointers:

https://wiki.archlinux.org/title/wpa_supplicant

https://w1.fi/cgit/hostap/plain/wpa_supplicant/README

https://w1.fi/cgit/hostap/tree/wpa_supplicant/wpa_supplicant.conf

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  reply	other threads:[~2024-04-25  9:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-09 15:08 QCA6174 showing terrible performance when connecting via WPA3-SAE Eric Park
2024-03-11 10:21 ` Kalle Valo
2024-03-21  4:05   ` Eric Park
2024-04-25  9:51     ` Kalle Valo [this message]
2024-04-28  3:04       ` Eric Park
2024-04-29 12:18         ` Kalle Valo
2024-04-29 13:26           ` Eric Park
2024-04-29 16:32             ` Kalle Valo
2024-04-29 17:53               ` Eric Park
2024-05-03 21:52                 ` Eric Park
2024-05-06  9:04                   ` Kalle Valo
2024-05-07  1:37                     ` Eric Park
2024-05-14 15:27                       ` Kalle Valo
2024-05-14 22:23                         ` Eric Park
2024-05-15  8:04                           ` Kalle Valo
2024-05-17  8:43                             ` Eric Park
2024-05-17  9:41                               ` Kalle Valo
2024-04-29 18:23           ` James Prestwood

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=87wmolsrcc.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath10k@lists.infradead.org \
    --cc=me@ericswpark.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.