From 5219e4ce8f9aa082c5f91e248a9f66639c69727d Mon Sep 17 00:00:00 2001 From: Martin Lucina Date: Fri, 28 May 2010 00:49:13 +0200 Subject: Clarify socket types in documentation, reinstate ZMQ_PAIR --- doc/zmq_setsockopt.txt | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'doc/zmq_setsockopt.txt') diff --git a/doc/zmq_setsockopt.txt b/doc/zmq_setsockopt.txt index 8845a10..3bc1081 100644 --- a/doc/zmq_setsockopt.txt +++ b/doc/zmq_setsockopt.txt @@ -61,13 +61,13 @@ The 'ZMQ_AFFINITY' option shall set the I/O thread affinity for connections created by subsequent _zmq_connect()_ or _zmq_bind()_ calls on the specified 'socket'. -sockets. Affinity determines which threads from the 0MQ I/O thread pool -associated with the socket's _context_ shall handle newly created connections. -A value of zero specifies no affinity, meaning that work shall be distributed -fairly among all 0MQ I/O threads in the thread pool. For non-zero values, the -lowest bit corresponds to thread 1, second lowest bit to thread 2 and so on. -For example, a value of 3 specifies that subsequent connections on 'socket' -shall be handled exclusively by I/O threads 1 and 2. +Affinity determines which threads from the 0MQ I/O thread pool associated with +the socket's _context_ shall handle newly created connections. A value of zero +specifies no affinity, meaning that work shall be distributed fairly among all +0MQ I/O threads in the thread pool. For non-zero values, the lowest bit +corresponds to thread 1, second lowest bit to thread 2 and so on. For example, +a value of 3 specifies that subsequent connections on 'socket' shall be handled +exclusively by I/O threads 1 and 2. See also linkzmq:zmq_init[3] for details on allocating the number of I/O threads for a specific _context_. -- cgit v1.2.3