[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f8bb65ed-cdf2-4d23-b794-765ce0b48a4b@acm.org>
Date: Thu, 22 Aug 2024 12:29:21 -0700
From: Bart Van Assche <bvanassche@....org>
To: mhklinux@...look.com, kbusch@...nel.org, axboe@...nel.dk,
sagi@...mberg.me, James.Bottomley@...senPartnership.com,
martin.petersen@...cle.com, kys@...rosoft.com, haiyangz@...rosoft.com,
wei.liu@...nel.org, decui@...rosoft.com, robin.murphy@....com, hch@....de,
m.szyprowski@...sung.com, petr@...arici.cz, iommu@...ts.linux.dev,
linux-kernel@...r.kernel.org, linux-nvme@...ts.infradead.org,
linux-scsi@...r.kernel.org, linux-hyperv@...r.kernel.org,
linux-coco@...ts.linux.dev
Subject: Re: [RFC 0/7] Introduce swiotlb throttling
On 8/22/24 11:37 AM, mhkelley58@...il.com wrote:
> Linux device drivers may make DMA map/unmap calls in contexts that
> cannot block, such as in an interrupt handler.
Although I really appreciate your work, what alternatives have been
considered? How many drivers perform DMA mapping from atomic context?
Would it be feasible to modify these drivers such that DMA mapping
always happens in a context in which sleeping is allowed?
Thanks,
Bart.
Powered by blists - more mailing lists