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

/linux-4.4.14/net/atm/
H A Dpppoatm.c118 * the wakeup *can't* race with pppoatm_send(). They both hold the PPP pppoatm_release_cb()
121 * exist here. In the sock_owned_by_user() case in pppoatm_send(), we pppoatm_release_cb()
145 * refuse another packet in pppoatm_send(). This was quite inefficient. pppoatm_pop()
147 * In fact it's OK. The PPP core will only ever call pppoatm_send() pppoatm_pop()
150 * CPU is in pppoatm_send() right now, the tasklet isn't going to race pppoatm_pop()
152 * of pppoatm_send() again. pppoatm_pop()
154 * So if the CPU in pppoatm_send() has already set the BLOCKED bit and pppoatm_pop()
156 * happen later. And if the CPU in pppoatm_send() *hasn't* set the pppoatm_pop()
273 * code path that calls pppoatm_send(), and is thus going to pppoatm_may_send()
292 static int pppoatm_send(struct ppp_channel *chan, struct sk_buff *skb) pppoatm_send() function
389 .start_xmit = pppoatm_send,

Completed in 36 milliseconds