All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: "Berg, Benjamin" <benjamin.berg@intel.com>
Cc: "chris.bainbridge@gmail.com" <chris.bainbridge@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Korenblit, Miriam Rachel" <miriam.rachel.korenblit@intel.com>,
	"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [REGRESSION] bisected: iwlwifi: use already mapped data when TXing an AMSDU
Date: Wed, 07 Aug 2024 17:18:38 +0300	[thread overview]
Message-ID: <87h6bwifgh.fsf@kernel.org> (raw)
In-Reply-To: <a98208c8123695c225ecf09915377fa19cb0fa0a.camel@intel.com> (Benjamin Berg's message of "Wed, 7 Aug 2024 13:59:55 +0000")

"Berg, Benjamin" <benjamin.berg@intel.com> writes:

> Hi,
>
> On Wed, 2024-08-07 at 16:49 +0300, Kalle Valo wrote:
>> Chris Bainbridge <chris.bainbridge@gmail.com> writes:
>> 
>> > On Wed, 7 Aug 2024 at 13:10, Kalle Valo <kvalo@kernel.org> wrote:
>> > > [SNIP]
>> > Not really. It is functional but tx throughput is severely
>> > degraded,
>> > iperf shows ~1mbit/sec instead of the usual ~600mbit. Rx throughput
>> > (measured with `iperf -c ... -R`) doesn't seem to be affected.
>> 
>> Ok, so a quite severe issue. Hopefully Intel can find a fix,
>> otherwise
>> we need to consider should we revert commit 90db50755228 ("wifi:
>> iwlwifi: use already mapped data when TXing an AMSDU") for v6.11.
>
> Yes, if we do not have a fix soon we'll need to revert. If so, then we
> should also revert:
>
> wifi: iwlwifi: keep the TSO and workaround pages mapped
> wifi: iwlwifi: map entire SKB when sending AMSDUs
>
> as well as the related bugfix:
> wifi: iwlwifi: correctly reference TSO page information
>
> Otherwise there is a performance impact as DMA mapping is effectively
> done twice.

That's good to know, thanks. But let's hope you find a fix.

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

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

  reply	other threads:[~2024-08-07 14:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-07 10:51 [REGRESSION] bisected: iwlwifi: use already mapped data when TXing an AMSDU Chris Bainbridge
2024-08-07 12:10 ` Kalle Valo
2024-08-07 12:34   ` Chris Bainbridge
2024-08-07 13:49     ` Kalle Valo
2024-08-07 13:59       ` Berg, Benjamin
2024-08-07 14:18         ` Kalle Valo [this message]
2024-08-07 12:42 ` Berg, Benjamin

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=87h6bwifgh.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=benjamin.berg@intel.com \
    --cc=chris.bainbridge@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=miriam.rachel.korenblit@intel.com \
    --cc=regressions@lists.linux.dev \
    /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.