Searched refs:callback_lock (Results 1 – 6 of 6) sorted by relevance
74 * - callback_lock (raw spinlock)91 * and internal variables can be modified without holding callback_lock. If only93 * hold either cpuset_mutex or callback_lock which are exposed to other97 * ensuring that it is the only task able to also acquire callback_lock and100 * without holding callback_lock. While it is performing these checks, various101 * callback routines can briefly acquire callback_lock to query cpusets. Once102 * it is ready to make the changes, it takes callback_lock, blocking everyone106 * callback_lock which is a spinlock, as the memory allocator may sleep or107 * call back into cpuset code and acquire callback_lock.113 * The cpuset_common_seq_show() handlers only hold callback_lock acros[all...]
177 spinlock_t callback_lock; member
1295 spin_lock_irqsave(&queue->callback_lock, flags); in xenvif_zerocopy_callback()1309 spin_unlock_irqrestore(&queue->callback_lock, flags); in xenvif_zerocopy_callback()
580 spin_lock_init(&queue->callback_lock); in xenvif_init_queue()
578 rwlock_init(&csk->callback_lock); in cxgbi_sock_create()847 read_lock_bh(&csk->callback_lock); in cxgbi_inform_iscsi_conn_closing()851 read_unlock_bh(&csk->callback_lock); in cxgbi_inform_iscsi_conn_closing()2704 write_lock_bh(&csk->callback_lock); in cxgbi_bind_conn()2709 write_unlock_bh(&csk->callback_lock); in cxgbi_bind_conn()2975 write_lock_bh(&csk->callback_lock); in cxgbi_ep_disconnect()2978 write_unlock_bh(&csk->callback_lock); in cxgbi_ep_disconnect()
161 rwlock_t callback_lock; member