From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: "Adrián Larumbe" <adrian.larumbe@collabora.com>,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, daniel@ffwll.ch,
robdclark@gmail.com, quic_abhinavk@quicinc.com,
dmitry.baryshkov@linaro.org, sean@poorly.run,
marijn.suijten@somainline.org, robh@kernel.org,
steven.price@arm.com
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, healych@amazon.com,
Boris Brezillon <boris.brezillon@collabora.com>,
kernel@collabora.com, freedreno@lists.freedesktop.org
Subject: Re: [PATCH v6 6/6] drm/drm-file: Show finer-grained BO sizes in drm_show_memory_stats
Date: Thu, 21 Sep 2023 11:14:27 +0100 [thread overview]
Message-ID: <6b9c8566-926d-40ff-7907-228d317fab3d@linux.intel.com> (raw)
In-Reply-To: <ccfa3697-b015-ff35-fb92-0efcbd1d7d7c@linux.intel.com>
On 20/09/2023 16:32, Tvrtko Ursulin wrote:
>
> On 20/09/2023 00:34, Adrián Larumbe wrote:
>> The current implementation will try to pick the highest available size
>> display unit as soon as the BO size exceeds that of the previous
>> multiplier. That can lead to loss of precision in contexts of low memory
>> usage.
>>
>> The new selection criteria try to preserve precision, whilst also
>> increasing the display unit selection threshold to render more accurate
>> values.
>>
>> Signed-off-by: Adrián Larumbe <adrian.larumbe@collabora.com>
>> Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
>> Reviewed-by: Steven Price <steven.price@arm.com>
>> ---
>> drivers/gpu/drm/drm_file.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/drm_file.c b/drivers/gpu/drm/drm_file.c
>> index 762965e3d503..34cfa128ffe5 100644
>> --- a/drivers/gpu/drm/drm_file.c
>> +++ b/drivers/gpu/drm/drm_file.c
>> @@ -872,6 +872,8 @@ void drm_send_event(struct drm_device *dev, struct
>> drm_pending_event *e)
>> }
>> EXPORT_SYMBOL(drm_send_event);
>> +#define UPPER_UNIT_THRESHOLD 100
>> +
>> static void print_size(struct drm_printer *p, const char *stat,
>> const char *region, u64 sz)
>> {
>> @@ -879,7 +881,8 @@ static void print_size(struct drm_printer *p,
>> const char *stat,
>> unsigned u;
>> for (u = 0; u < ARRAY_SIZE(units) - 1; u++) {
>> - if (sz < SZ_1K)
>> + if ((sz & (SZ_1K - 1)) &&
>
> IS_ALIGNED worth it at all?
>
>> + sz < UPPER_UNIT_THRESHOLD * SZ_1K)
>> break;
>
> Excuse me for a late comment (I was away). I did not get what what is
> special about a ~10% threshold? Sounds to me just going with the lower
> unit, when size is not aligned to the higher one, would be better than
> sometimes precision-sometimes-not.
FWIW both current and the threshold option make testing the feature very
annoying.
So I'd really propose we simply use smaller unit when unaligned.
Regards,
Tvrtko
next prev parent reply other threads:[~2023-09-21 21:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 23:34 [PATCH v6 0/6] Add fdinfo support to Panfrost Adrián Larumbe
2023-09-19 23:34 ` [PATCH v6 1/6] drm/panfrost: Add cycle count GPU register definitions Adrián Larumbe
2023-09-19 23:34 ` [PATCH v6 2/6] drm/panfrost: Add fdinfo support GPU load metrics Adrián Larumbe
2023-09-20 15:40 ` Tvrtko Ursulin
2023-09-22 10:57 ` Adrián Larumbe
2023-09-22 13:53 ` Tvrtko Ursulin
2023-09-22 15:23 ` Steven Price
2023-09-25 8:57 ` Tvrtko Ursulin
2023-09-19 23:34 ` [PATCH v6 3/6] drm/panfrost: Add fdinfo support for memory stats Adrián Larumbe
2023-09-19 23:34 ` [PATCH v6 4/6] drm/drm_file: Add DRM obj's RSS reporting function for fdinfo Adrián Larumbe
2023-09-20 15:53 ` Tvrtko Ursulin
2023-09-22 10:58 ` Adrián Larumbe
2023-09-27 14:36 ` Tvrtko Ursulin
2023-09-19 23:34 ` [PATCH v6 5/6] drm/panfrost: Implement generic DRM object RSS reporting function Adrián Larumbe
2023-09-19 23:34 ` [PATCH v6 6/6] drm/drm-file: Show finer-grained BO sizes in drm_show_memory_stats Adrián Larumbe
2023-09-20 15:32 ` Tvrtko Ursulin
2023-09-21 10:14 ` Tvrtko Ursulin [this message]
2023-09-22 11:03 ` Adrián Larumbe
2023-09-22 14:02 ` Tvrtko Ursulin
2023-09-22 11:01 ` Adrián Larumbe
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=6b9c8566-926d-40ff-7907-228d317fab3d@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=adrian.larumbe@collabora.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=healych@amazon.com \
--cc=kernel@collabora.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=mripard@kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robh@kernel.org \
--cc=sean@poorly.run \
--cc=steven.price@arm.com \
--cc=tzimmermann@suse.de \
/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