From: Johannes Berg <johannes@sipsolutions.net>
To: Baochen Qiang <quic_bqiang@quicinc.com>,
Fabio Estevam <festevam@gmail.com>
Cc: miriam.rachel.korenblit@intel.com, kvalo@kernel.org,
Jakub Kicinski <kuba@kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: iwlwifi: Regression after migrating to 6.6.32
Date: Thu, 13 Jun 2024 12:36:59 +0200 [thread overview]
Message-ID: <6e556f7b6b769c4d70be3e248b98d8d09d51452b.camel@sipsolutions.net> (raw)
In-Reply-To: <35750452-e362-4dfa-803a-3360a4e16cd8@quicinc.com>
On Thu, 2024-06-13 at 17:51 +0800, Baochen Qiang wrote:
> >
> > Not sure that means anything though, I really would have expected a 4k
> > buffer to be 4k aligned - why would you even want to map it across two
> > pages?
> IMO SWIOTLB manages buffers in a unit of IO_TLB_SIZE, it does not care about whether or not we are crossing page boundaries, no?
Well arguably it should have some 'natural' alignment guarantees?
> >
> > If it is SWIOTLB, shouldn't we get into this condition?
> >
> > /*
> > * Historically, swiotlb allocations >= PAGE_SIZE were guaranteed to be
> > * page-aligned in the absence of any other alignment requirements.
> > * 'alloc_align_mask' was later introduced to specify the alignment
> > * explicitly, however this is passed as zero for streaming mappings
> > * and so we preserve the old behaviour there in case any drivers are
> > * relying on it.
> > */
> > if (!alloc_align_mask && !iotlb_align_mask && alloc_size >= PAGE_SIZE)
> > alloc_align_mask = PAGE_SIZE - 1;
> >
> This is not present in 6.6.32 stable kernel.
>
Oh. So I guess try to pick up commit 14cebf689a78 ("swiotlb: Reinstate
page-alignment for mappings >= PAGE_SIZE").
johannes
next prev parent reply other threads:[~2024-06-13 10:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 11:46 Fabio Estevam
2024-06-11 12:52 ` Johannes Berg
2024-06-11 13:43 ` Fabio Estevam
2024-06-11 13:54 ` Johannes Berg
2024-06-11 14:32 ` Fabio Estevam
2024-06-11 14:50 ` Johannes Berg
2024-06-11 14:59 ` Fabio Estevam
2024-06-12 19:10 ` Johannes Berg
2024-06-12 19:15 ` Fabio Estevam
2024-06-13 6:58 ` Johannes Berg
2024-06-13 7:10 ` Baochen Qiang
2024-06-13 7:40 ` Johannes Berg
2024-06-13 9:51 ` Baochen Qiang
2024-06-13 10:36 ` Johannes Berg [this message]
2024-06-13 20:15 ` Fabio Estevam
2024-06-17 12:08 ` Will Deacon
2024-06-17 14:08 ` Fabio Estevam
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=6e556f7b6b769c4d70be3e248b98d8d09d51452b.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=festevam@gmail.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
--cc=quic_bqiang@quicinc.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
all inboxes | Powered by JetHome®