Skip to contentSkip to conversation

is it useful testing __LINK_STATE_RX_SCHED in dev_close()?

DISCUSSION [email protected] 2 participants 2 messages Nov 20, 2007

lore
Share & tools
lore
#0 lore raw

cpu0 calling netif_rx_schedule_prep(), cpu1 calling dev_close():

cpu0: testing __LINK_STATE_START, already set
cpu1: clear__LINK_STATE_START
cpu1: testing __LINK_STATE_RX_SCHED, not set
cpu0: set __LINK_STATE_RX_SCHED
cpu0: enter net poll, ...

when cpu1 return from dev_close(),__LINK_STATE_RX_SCHED is still set.

#1 lore raw

From: <[email protected]>
Date: Tue, 20 Nov 2007 18:26:26 +0800

Quoted 9 lines

cpu0 calling netif_rx_schedule_prep(), cpu1 calling dev_close():

cpu0: testing __LINK_STATE_START, already set
cpu1: clear__LINK_STATE_START
cpu1: testing __LINK_STATE_RX_SCHED, not set
cpu0: set __LINK_STATE_RX_SCHED
cpu0: enter net poll, ...

when cpu1 return from dev_close(),__LINK_STATE_RX_SCHED is still set.

You'll have better luck asking networking questions on [email protected] as that is the mailing list where the kernel networking developers are subscribed.