From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OpenGL and LWT
Date: Mon, 17 Mar 2014 12:01:37 +0100 [thread overview]
Message-ID: <BD67404BD6464EA395549A97A56AB9D1@erratique.ch> (raw)
In-Reply-To: <5326CFA2.909@etorok.net>
Le lundi, 17 mars 2014 à 11:34, Török Edwin a écrit :
> Well there are a few that are slow, like swapping buffers which can wait for vsync.
Yes and you should make sure that the C bindings to these calls release the ocaml runtime system lock during the call. Other slow calls are memory transfer calls (e.g. glBufferData). This book chapter [1] may be worth reading.
Daniel
[1] http://www.seas.upenn.edu/~pcozzi/OpenGLInsights/OpenGLInsights-AsynchronousBufferTransfers.pdf
prev parent reply other threads:[~2014-03-17 11:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 17:37 Richard Neswold
2014-03-17 10:09 ` Jeremie Dimino
2014-03-17 10:32 ` Ivan Gotovchits
2014-03-17 13:39 ` Rich Neswold
2014-03-17 14:05 ` Daniel Bünzli
2014-03-17 14:13 ` Daniel Bünzli
2014-03-17 22:50 ` Richard Neswold
2014-03-17 23:50 ` Daniel Bünzli
2014-03-19 12:01 ` Rich Neswold
2014-03-17 10:34 ` Török Edwin
2014-03-17 11:01 ` Daniel Bünzli [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=BD67404BD6464EA395549A97A56AB9D1@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@inria.fr \
/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).