From: Thomas Zimmermann <tzimmermann@suse.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: airlied@linux.ie, ray.huang@amd.com,
linux-graphics-maintainer@vmware.com, christian.koenig@amd.com,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/vmwgfx: Copy DRM hash-table code into driver
Date: Tue, 16 Nov 2021 10:11:52 +0100 [thread overview]
Message-ID: <e162217a-a605-d284-e142-5132fa5cbb9d@suse.de> (raw)
In-Reply-To: <YZKKY2wQS7SEujPh@ravnborg.org>
[-- Attachment #1.1: Type: text/plain, Size: 1424 bytes --]
Hi Sam
Am 15.11.21 um 17:27 schrieb Sam Ravnborg:
> Hi Thomas,
>
> On Mon, Nov 15, 2021 at 01:55:38PM +0100, Thomas Zimmermann wrote:
>> Besides some legacy code, vmwgfx is the only user of DRM's hash-
>> table implementation. Copy the code into the driver, so that the
>> core code can be retired.
> For the record - I have no clue what legacy code uses the DRM hash-table
> for.
>
>>
>> No functional changes. However, the real solution for vmwgfx is to
>> use Linux' generic hash-table functions.
> Would it be possible to use the Linux hash-table now rather than this
> mid-step where a lot of code is added to wmgfx only to be removed
> later?
I indeed considered to replace the hashtable with Linux' implementation.
But the differences are slightly more involved than just API changes and
a hashtable's performance often depends on its configuration. In the
end, I didn't feel confident enough to make this change without doing
damage.
>
> If we go for this way then a todo item to fix this in wmgfx so someone
> can fix this later would be nice.
Sure. I'll add one. Zack already seems interested in having someone from
his team working on it.
Best regards
Thomas
>
> Sam
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2021-11-16 9:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 12:55 [PATCH 0/3] drm: Make DRM hashtable legacy Thomas Zimmermann
2021-11-15 12:55 ` [PATCH 1/3] drm/ttm: Don't include drm_hashtab.h Thomas Zimmermann
2021-11-15 13:28 ` Christian König
2021-11-15 12:55 ` [PATCH 2/3] drm/vmwgfx: Copy DRM hash-table code into driver Thomas Zimmermann
2021-11-15 14:33 ` Daniel Vetter
2021-11-15 16:27 ` Sam Ravnborg
2021-11-16 9:11 ` Thomas Zimmermann [this message]
2021-11-15 17:00 ` Zack Rusin
2021-11-16 9:20 ` Thomas Zimmermann
2021-11-15 12:55 ` [PATCH 3/3] drm: Declare hashtable as legacy Thomas Zimmermann
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=e162217a-a605-d284-e142-5132fa5cbb9d@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=ray.huang@amd.com \
--cc=sam@ravnborg.org \
/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.