Check out my first novel, midnight's simulacra!

Libtorque: Difference between revisions

From dankwiki
No edit summary
No edit summary
Line 1: Line 1:
My project for Professor Rich Vuduc's [[High Performance Parallel Computing|CSE6230]] in Fall 2009, libtorque is a multithreaded event library for UNIX targeted towards manycore NUMA machines. Previous, non-threaded event libraries include libevent, libev and liboop. My [http://dank.qemfd.net/tabpower/cse6230proposal.pdf project proposal] explains motivation for libtorque: it is necessary to take scheduling and memory-placement decisions into account to most optimally handle events, especially on manycore machines and ''especially'' to handle unexpected traffic sets (denial of service attacks, oversubscribed pipes, mixed-latency connections, etc).
My project for Professor Rich Vuduc's [[High Performance Parallel Computing|CSE6230]] in Fall 2009, libtorque is a multithreaded event library for UNIX targeted towards manycore [[NUMA]] machines. Previous, non-threaded event libraries include libevent, libev and liboop. My [http://dank.qemfd.net/tabpower/cse6230proposal.pdf project proposal] explains motivation for libtorque: it is necessary to take scheduling and memory-placement decisions into account to most optimally handle events, especially on manycore machines and ''especially'' to handle unexpected traffic sets (denial of service attacks, oversubscribed pipes, mixed-latency connections, etc).


==Milestones==
==Milestones==
* 2009-11-19: CSE 6230 checkpoint
* 2009-11-19: CSE 6230 checkpoint
* 2009-12-10: CSE 6230 due date
* 2009-12-10: CSE 6230 due date

Revision as of 03:28, 23 October 2009

My project for Professor Rich Vuduc's CSE6230 in Fall 2009, libtorque is a multithreaded event library for UNIX targeted towards manycore NUMA machines. Previous, non-threaded event libraries include libevent, libev and liboop. My project proposal explains motivation for libtorque: it is necessary to take scheduling and memory-placement decisions into account to most optimally handle events, especially on manycore machines and especially to handle unexpected traffic sets (denial of service attacks, oversubscribed pipes, mixed-latency connections, etc).

Milestones

  • 2009-11-19: CSE 6230 checkpoint
  • 2009-12-10: CSE 6230 due date