Searched refs:max_active (Results 1 - 7 of 7) sorted by relevance

/freebsd-11-stable/contrib/unbound/daemon/
H A Dremote.h99 int max_active; member in struct:daemon_remote
H A Dremote.c206 rc->max_active = 10;
458 if(rc->active >= rc->max_active) {
/freebsd-11-stable/sys/compat/linuxkpi/common/include/linux/
H A Dworkqueue.h159 #define alloc_workqueue(name, flags, max_active) \
160 linux_create_workqueue_common(name, max_active)
/freebsd-11-stable/sys/ofed/drivers/infiniband/core/
H A Dmad_priv.h183 int max_active; member in struct:ib_mad_queue
H A Dib_mad.c1189 if (qp_info->send_queue.count < qp_info->send_queue.max_active) {
2474 if (send_queue->count-- > send_queue->max_active) {
2902 post = (++recv_queue->count < recv_queue->max_active);
3106 qp_info->send_queue.max_active = mad_sendq_size;
3107 qp_info->recv_queue.max_active = mad_recvq_size;
H A Dib_mad_rmpp.c409 return max(agent->qp_info->recv_queue.max_active >> 3, 1);
/freebsd-11-stable/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/
H A Dvdev_queue.c120 * the sum of each queue's max_active. It must be at least the sum of each
127 * sum of the queue's max_active is < zfs_vdev_max_active, then the
131 * In general, smaller max_active's will lead to lower latency of synchronous
132 * operations. Larger max_active's may lead to higher overall throughput,
228 SYSCTL_UINT(_vfs_zfs_vdev, OID_AUTO, max_active, CTLFLAG_RWTUN,

Completed in 202 milliseconds