From: Robin Murphy <robin.murphy@arm.com>
To: Christoph Hellwig <hch@lst.de>, Tim Harvey <tharvey@gateworks.com>
Cc: Baochen Qiang <quic_bqiang@quicinc.com>,
ath11k@lists.infradead.org,
linux-wireless <linux-wireless@vger.kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
iommu@lists.linux.dev
Subject: Re: ath11k swiotlb buffer is full (on IMX8M with 4GiB DRAM)
Date: Mon, 9 Dec 2024 10:49:49 +0000 [thread overview]
Message-ID: <593c0d63-d8fd-4439-a57a-97340212c197@arm.com> (raw)
In-Reply-To: <20241209081714.GA25363@lst.de>
On 09/12/2024 8:17 am, Christoph Hellwig wrote:
> I scrolled three pages before giving up as it was just quotes over
> quotas. Can you please write an email that contains whatever you're
> trying to tell instead of just quotes? Same for the person replying.
TBH I'm hesitant to look too closely since everything those Atheros WiFi
drivers do with DMA tends to be sketchy, but from what I could make out
from skimming until I also gave up, I think it might be an attempt to
reinvent dma_alloc_pages(), or possibly dma_alloc_noncoherent().
Cheers,
Robin.
next prev parent reply other threads:[~2024-12-09 10:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 0:43 ath11k swiotlb buffer is full (on IMX8M with 4GiB DRAM) Tim Harvey
2024-11-25 7:23 ` Baochen Qiang
2024-11-25 18:02 ` Tim Harvey
2024-11-26 2:46 ` Baochen Qiang
2024-12-06 17:07 ` Tim Harvey
2024-12-09 6:39 ` Baochen Qiang
2024-12-09 8:17 ` Christoph Hellwig
2024-12-09 10:49 ` Robin Murphy [this message]
2024-12-09 19:15 ` Tim Harvey
2024-12-10 4:11 ` Christoph Hellwig
2024-12-10 23:06 ` Tim Harvey
2024-12-11 2:31 ` Baochen Qiang
2024-12-11 13:44 ` Robin Murphy
2024-12-12 5:24 ` Baochen Qiang
2024-12-12 7:18 ` Christoph Hellwig
2024-12-12 18:08 ` Jeff Johnson
2024-12-12 19:57 ` Tim Harvey
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=593c0d63-d8fd-4439-a57a-97340212c197@arm.com \
--to=robin.murphy@arm.com \
--cc=ath11k@lists.infradead.org \
--cc=festevam@gmail.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=linux-wireless@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=quic_bqiang@quicinc.com \
--cc=tharvey@gateworks.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.