From: Jeremie Dimino <jdimino@janestreet.com>
To: Richard Neswold <rich.neswold@gmail.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] OpenGL and LWT
Date: Mon, 17 Mar 2014 10:09:26 +0000 [thread overview]
Message-ID: <CANhEzE4k5unUmDbT+1GsC8BQnt7LPt2QSdM=_joa6d6BKdETUA@mail.gmail.com> (raw)
In-Reply-To: <1732E7D3-C154-4305-90C8-0CC292FE08CF@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
Hi,
On Sat, Mar 15, 2014 at 5:37 PM, Richard Neswold <rich.neswold@gmail.com>wrote:
> Hello,
>
> What would be the appropriate way to use LWT and LabGL together?
>
> My gut feeling would be to have the core model and logic to be LWT with a
> 'detached' thread executing the OpenGL main loop. The thread would get
> events through the reactive module and would update the display accordingly.
>
> The problem is I'm still trying to wrap my head around LWT and I'm not
> sure a detached thread can participate with the LWT environment it was
> spawned from. It appears the detached thread is supposed to do something
> and eventually return a value.
>
Yes, the purpose of Lwt_preemptive.detach is to execute a blocking action
in a separate system thread in order not to block all lwt threads. And from
another system thread you cannot run lwt code directly, you have to use
Lwt_preemptive.run_in_main.
> Is the correct approach to use a detached thread to make the individual
> OpenGL calls?
>
I think that would be very slow, as in involves system thread
synchronization.
> Any recommendations or resources on the subject would be appreciated.
>
You could try to assume that OpenGL calls are fast and perform them in the
same thread as lwt.
--
Jeremie
[-- Attachment #2: Type: text/html, Size: 1978 bytes --]
next prev parent reply other threads:[~2014-03-17 10:09 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 [this message]
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
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='CANhEzE4k5unUmDbT+1GsC8BQnt7LPt2QSdM=_joa6d6BKdETUA@mail.gmail.com' \
--to=jdimino@janestreet.com \
--cc=caml-list@inria.fr \
--cc=rich.neswold@gmail.com \
/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