From: David Miller <davem@davemloft.net>
To: wyb@topsec.com.cn
Cc: linux-kernel@vger.kernel.org
Subject: Re: is it useful testing __LINK_STATE_RX_SCHED in dev_close()?
Date: Tue, 20 Nov 2007 02:42:27 -0800 (PST) [thread overview]
Message-ID: <20071120.024227.121377069.davem@davemloft.net> (raw)
In-Reply-To: <200711201028.AYF43414@topsec.com.cn>
From: <wyb@topsec.com.cn>
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: 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
netdev@vger.kernel.org as that is the mailing list where
the kernel networking developers are subscribed.
prev parent reply other threads:[~2007-11-20 10:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 10:26 wyb
2007-11-20 10:42 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071120.024227.121377069.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wyb@topsec.com.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®