ThreadPool.BindHandle

Multithreading: I/O and the thread pool

ASPInsiders — Thu, 04 Jun 2009 16:22:18 GMT

When we started looking at how we could use the thread pool for asynchronous work, I (only!) mentioned

Multithreading: I/O and the thread pool

LA.NET [EN] — Thu, 04 Jun 2009 16:10:24 GMT

When we started looking at how we could use the thread pool for asynchronous work, I (only!) mentioned

re: ThreadPool.BindHandle

Jelle Hissink — Thu, 04 Dec 2008 19:07:18 GMT

junfeng,

thanks for pointing it out, I must have somehow missed that while reading the documentation.

re: ThreadPool.BindHandle

Junfeng Zhang — Thu, 04 Dec 2008 01:03:14 GMT

In step 4,

NativeOverlapped* pOverlapped = overlapped.Pack(iocomplete, bytes);

This statement implicitly pins the bytes object. The object is unpinned when the overlap is freed.

re: ThreadPool.BindHandle

Jelle Hissink — Wed, 03 Dec 2008 22:54:23 GMT

JM,

Thanks for the pointer tot the GCHandle, hadn't seen that class before. Till now I always try to allocate a buffer using Marshal.MAlloc and reuse it for multiple reads.

re: ThreadPool.BindHandle

JM — Wed, 03 Dec 2008 15:21:48 GMT

@Jelle: you're quite right. Using Marshal every time is slow, though. A better approach is to allocate a GCHandle with type GCHandleType.Pinned, which will prevent the GC from moving the array (and collecting it, incidentally).

re: ThreadPool.BindHandle

Jelle Hissink — Wed, 03 Dec 2008 00:34:38 GMT

In step 5 when you leave the fixed {} block the p is free to be moved by the GC. Doesn't this buffer needs to be allocated using Marshall.MAlloc and freed after the read has finished?

Regards

infoblog » ThreadPool.BindHandle

infoblog » ThreadPool.BindHandle — Mon, 01 Dec 2008 19:12:19 GMT

PingBack from http://blog.a-foton.ru/index.php/2008/12/01/threadpoolbindhandle/