[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20240428172919.691602-1-liujianfeng1994@gmail.com>
Date: Mon, 29 Apr 2024 01:29:19 +0800
From: Jianfeng Liu <liujianfeng1994@...il.com>
To: heiko@...ech.de
Cc: andy.yan@...k-chips.com,
conor+dt@...nel.org,
cristian.ciocaltea@...labora.com,
devicetree@...r.kernel.org,
dsimic@...jaro.org,
ezequiel@...guardiasur.com.ar,
frattaroli.nicolas@...il.com,
iommu@...ts.linux.dev,
joro@...tes.org,
krzysztof.kozlowski+dt@...aro.org,
linkmauve@...kmauve.fr,
linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
linux-media@...r.kernel.org,
linux-rockchip@...ts.infradead.org,
liujianfeng1994@...il.com,
macromorgan@...mail.com,
mchehab@...nel.org,
nicolas@...fresne.ca,
p.zabel@...gutronix.de,
robh@...nel.org,
robin.murphy@....com,
sebastian.reichel@...labora.com,
shreeya.patel@...labora.com,
sigmaris@...il.com,
will@...nel.org
Subject: Re: [PATCH v4 0/2] Enable JPEG encoding on rk3588
Hi Heiko,
On Sun, 28 Apr 2024 19:01:38 +0200, Heiko Stübner wrote:
>the basic problem is that exposing multiple jpeg encoders would require
>userspace to do the scheduling. Which is bad.
>I.e. all userspace programms would need to know the existence of
>all jpeg encoders and then somehow negotiate how to use all of them
>most efficiently.
>
>Think multiple different programs that would need to negotiate to
>spread across all of them in the best way.
>
>Doing this in the kernel, we just expose one encoder (and queue) all
>programs would just pile onto that one encoder and the kernel then
>would be on the hook to do the scheduling - which the kernel can do
>better (with relevant code implemented)
Yeah let kernel do the scheduling is indeed better. And I'm happy to
hear this method.
So I will keep the vpu at feb50000 with jpeg endoder disabled until
multi encoder scheduling is implemented.
Best regards,
Jianfeng
Powered by blists - more mailing lists