From: "Enrico Weigelt, metux IT consult" <enrico.weigelt@gr13.net>
To: dri devel <dri-devel@lists.freedesktop.org>
Subject: Frame buffer access performance
Date: Fri, 5 Aug 2016 04:35:25 +0200 [thread overview]
Message-ID: <57A3FB6D.8060807@gr13.net> (raw)
Hi folks,
when putting pixels into an DRM framebuffer, should I do that in
bursts/blocks instead of byte-per-byte ? (eg. explicitly using
aligned 32bit ops).
--mtx
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-08-05 2:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 2:35 Enrico Weigelt, metux IT consult [this message]
2016-08-05 8:15 ` Frame buffer access performance Daniel Vetter
2016-08-05 9:04 ` Enrico Weigelt, metux IT consult
2016-08-05 9:23 ` Daniel Vetter
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=57A3FB6D.8060807@gr13.net \
--to=enrico.weigelt@gr13.net \
--cc=dri-devel@lists.freedesktop.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