From: "Philip Silva via 9fans" <9fans@9fans.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] suggestion : new service targets for plan9
Date: Fri, 28 Jan 2022 14:11:12 +0000 [thread overview]
Message-ID: <7Ad_k2SFVPp1bxcNqGCiOKNrQceD7FS-YAAtZs2SMCoPk8DELtakra290--rxDS7haPlflgT5a4a_ePOTjSNHxpqe_FaenTWFnAgp4SEmp0=@protonmail.com> (raw)
In-Reply-To: <16433724910.4fa96.617630@composer.9fans.topicbox.com>
Also of course it depends on what needs to be rendered. I didn't deep-dive yet into the internals of it, but isn't it that when combining the images at the end, that transfer of the initial images with lots of data basically happens only once? It seems to me devdraw can be quite performant on certain use cases. (UIs with basic shapes) But true, having access to the framebuffer should offer more options. Also I wonder what kind of functions it should be providing. (And if devdraw couldn't be just made faster)
> What I suggest is a lower level interface to use the framebuffer directly and I think devdraw (memdraw, memlayer) is too high level and rio oriented. ... Also the transfer of images in this way is expensive (regarding time) a screen image is at least copied two times. So by defining a lower level we could improve the performance of rendering by a factor of two.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T2518f9e4fc10ed03-M3f8fff74c67b09c5e2cde53f
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-01-28 14:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 2:03 ibrahim via 9fans
2022-01-28 5:22 ` ori
2022-01-28 11:38 ` ibrahim via 9fans
2022-01-28 7:50 ` vic.thacker
2022-01-28 11:49 ` ibrahim via 9fans
2022-01-28 9:55 ` Frank D. Engel, Jr.
2022-01-28 12:13 ` sirjofri
2022-01-28 12:21 ` ibrahim via 9fans
2022-01-28 14:11 ` Philip Silva via 9fans [this message]
2022-01-28 15:27 ` ibrahim via 9fans
2022-01-28 15:44 ` ibrahim via 9fans
2022-01-28 15:49 ` ori
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='7Ad_k2SFVPp1bxcNqGCiOKNrQceD7FS-YAAtZs2SMCoPk8DELtakra290--rxDS7haPlflgT5a4a_ePOTjSNHxpqe_FaenTWFnAgp4SEmp0=@protonmail.com' \
--to=9fans@9fans.net \
/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 NNTP newsgroup(s).