subject:"is it useful testing __LINK_STATE_RX_SCHED in dev_close\(\)\?"

Re: is it useful testing __LINK_STATE_RX_SCHED in dev_close()?

2007-11-20 Thread David Miller

From: <[EMAIL PROTECTED]> Date: Tue, 20 Nov 2007 18:26:26 +0800 > 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 >

is it useful testing __LINK_STATE_RX_SCHED in dev_close()?

2007-11-20 Thread wyb

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

is it useful testing __LINK_STATE_RX_SCHED in dev_close()?

2007-11-20 Thread wyb

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

Re: is it useful testing __LINK_STATE_RX_SCHED in dev_close()?

2007-11-20 Thread David Miller

From: [EMAIL PROTECTED] Date: Tue, 20 Nov 2007 18:26:26 +0800 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: