[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220305000337.24995-1-miles.chen@mediatek.com>
Date: Sat, 5 Mar 2022 08:03:37 +0800
From: Miles Chen <miles.chen@...iatek.com>
To: <robin.murphy@....com>
CC: <iommu@...ts.linux-foundation.org>, <joro@...tes.org>,
<linux-kernel@...r.kernel.org>, <miles.chen@...iatek.com>,
<stable@...r.kernel.org>, <will@...nel.org>,
<wsd_upstream@...iatek.com>, <yf.wang@...iatek.com>
Subject: Re: [PATCH] iommu/iova: Improve 32-bit free space estimate
Hi Joerg, Robin,
> Applied without stable tag for now. If needed, please consider
> re-sending it for stable when this patch is merged upstream.
> Yeah, having figured out the history, I ended up with the opinion that
> it was a missed corner-case optimisation opportunity, rather than an
> actual error with respect to intent or implementation, so I
> intentionally left that out. Plus figuring out an exact Fixes tag might
> be tricky - as above I reckon it probably only started to become
> significant somwehere around 5.11 or so.
>
> All of these various levels of retry mechanisms are only a best-effort
> thing, and ultimately if you're making large allocations from a small
> space there are always going to be *some* circumstances that still
> manage to defeat them. Over time, we've made them try harder, but that
> fact that we haven't yet made them try hard enough to work well for a
> particular use-case does not constitute a bug. However as Joerg says,
> anyone's welcome to make a case to Greg to backport a mainline commit if
> it's a low-risk change with significant benefit to real-world stable
> kernel users.
Got it, thank you.
We will try to push to the android LTS trees we need.
Thanks,
Miles
>
> Thanks all!
>
> Robin.
Powered by blists - more mailing lists