00:01:19  * Fishrock123joined
00:05:52  * Fishrock123quit (Ping timeout: 258 seconds)
03:17:58  * Fishrock123joined
03:23:11  * Fishrock123quit (Ping timeout: 264 seconds)
03:39:54  * brsonquit (Quit: leaving)
09:41:41  * rendarjoined
09:56:27  * madgoatjoined
09:57:54  * madgoatquit (K-Lined)
10:02:30  * zju_xjoined
12:29:25  * zju_xquit (Ping timeout: 268 seconds)
17:33:27  * zju_xjoined
17:40:24  * npsjoined
17:41:53  * npsquit (Client Quit)
18:24:44  <Cheery>does libuv support passing a HANDLE between applications?
18:33:39  <indutny>through IPC pipes
18:33:52  <indutny>some kind of handles may be passed
18:34:04  <indutny>probably all of them, although I'm not a windows expert
18:38:18  <Cheery>Vulkan provides some nifty extensions for inter-process communication over the GPU.
18:38:34  <Cheery>but it's divided and it's using file handles.
18:38:37  <Cheery>VK_KHX_external_memory_fd
18:38:44  <Cheery>VK_KHX_external_memory_win32
18:39:21  <Cheery>it's got a vkGetMemoryWin32HandleKHX that gives you a HANDLE
18:39:43  <Cheery>and vkGetMemoryFdKHX that gives you a int
18:40:47  <Cheery>the receiving process must retrieve the handle and allocate with it.
18:40:58  <Cheery>I wonder if uv_write2 would work for this.
18:41:37  <Cheery>on linux, I guess it probably does?
18:41:57  <Cheery>on windows?
18:48:07  <Cheery>mm.. I'll try that out in few moments. :)
18:52:21  <indutny>it should
18:52:34  <indutny>the only important thing to keep in mind
18:52:45  <indutny>is that IPC pipe should be managed by libuv on both ends
18:52:55  <indutny>because it wraps messages to be able to send handles
19:38:58  * zju_x1joined
19:40:56  * zju_xquit (Ping timeout: 240 seconds)
19:41:32  * zju_x1changed nick to zju_x
21:45:02  * rendarquit (Ping timeout: 268 seconds)
22:14:02  * rendarjoined
22:14:02  * rendarquit (Changing host)
22:14:02  * rendarjoined