From: Jianfeng Liu <liujianfeng1994@gmail.com>
To: heiko@sntech.de
Cc: andy.yan@rock-chips.com, conor+dt@kernel.org,
cristian.ciocaltea@collabora.com, devicetree@vger.kernel.org,
dsimic@manjaro.org, ezequiel@vanguardiasur.com.ar,
frattaroli.nicolas@gmail.com, iommu@lists.linux.dev,
joro@8bytes.org, krzysztof.kozlowski+dt@linaro.org,
linkmauve@linkmauve.fr, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-rockchip@lists.infradead.org, liujianfeng1994@gmail.com,
macromorgan@hotmail.com, mchehab@kernel.org,
nicolas@ndufresne.ca, p.zabel@pengutronix.de, robh@kernel.org,
robin.murphy@arm.com, sebastian.reichel@collabora.com,
shreeya.patel@collabora.com, sigmaris@gmail.com, will@kernel.org
Subject: Re: [PATCH v4 0/2] Enable JPEG encoding on rk3588
Date: Mon, 29 Apr 2024 01:29:19 +0800 [thread overview]
Message-ID: <20240428172919.691602-1-liujianfeng1994@gmail.com> (raw)
In-Reply-To: <3784322.QJadu78ljV@diego>
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
prev parent reply other threads:[~2024-04-28 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 14:15 [PATCH v4 0/2] Enable JPEG encoding on rk3588 Emmanuel Gil Peyrot
2024-04-18 14:15 ` [PATCH v4 1/2] media: dt-binding: Document rk3588’s VEPU121 Emmanuel Gil Peyrot
2024-04-18 14:15 ` [PATCH v4 2/2] arm64: dts: rockchip: Add one VEPU121 to rk3588 Emmanuel Gil Peyrot
2024-04-27 7:16 ` [PATCH v4 0/2] Enable JPEG encoding on rk3588 Jianfeng Liu
2024-04-28 17:01 ` Heiko Stübner
2024-04-28 17:29 ` Jianfeng Liu [this message]
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=20240428172919.691602-1-liujianfeng1994@gmail.com \
--to=liujianfeng1994@gmail.com \
--cc=andy.yan@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=frattaroli.nicolas@gmail.com \
--cc=heiko@sntech.de \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linkmauve@linkmauve.fr \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=macromorgan@hotmail.com \
--cc=mchehab@kernel.org \
--cc=nicolas@ndufresne.ca \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sebastian.reichel@collabora.com \
--cc=shreeya.patel@collabora.com \
--cc=sigmaris@gmail.com \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).