[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <543345ac-fbfa-1020-b6c7-72f65412f444@acm.org>
Date: Wed, 8 Jun 2022 10:27:59 -0700
From: Bart Van Assche <bvanassche@....org>
To: John Garry <john.garry@...wei.com>,
damien.lemoal@...nsource.wdc.com, joro@...tes.org, will@...nel.org,
jejb@...ux.ibm.com, martin.petersen@...cle.com, hch@....de,
m.szyprowski@...sung.com, robin.murphy@....com
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-ide@...r.kernel.org, iommu@...ts.linux-foundation.org,
linux-scsi@...r.kernel.org, liyihang6@...ilicon.com,
chenxiang66@...ilicon.com, thunder.leizhen@...wei.com
Subject: Re: [PATCH v3 1/4] dma-mapping: Add dma_opt_mapping_size()
On 6/6/22 02:30, John Garry wrote:
> +::
> +
> + size_t
> + dma_opt_mapping_size(struct device *dev);
> +
> +Returns the maximum optimal size of a mapping for the device. Mapping large
> +buffers may take longer so device drivers are advised to limit total DMA
> +streaming mappings length to the returned value.
"Maximum optimal" sounds weird to me. Is there a single optimal value or
are there multiple optimal values? In the former case I think that the
word "maximum" should be left out.
Thanks,
Bart.
Powered by blists - more mailing lists