From: Ben Hutchings <bhutchings@solarflare.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <shemminger@vyatta.com>,
<shchepetkov@ispras.ru>, <bjorn@mork.no>, <mike@marineau.org>
Subject: Re: [PATCH net-next] net: Set device operstate at registration time
Date: Fri, 24 Aug 2012 17:53:55 +0100 [thread overview]
Message-ID: <1345827235.2694.12.camel@bwh-desktop.uk.solarflarecom.com> (raw)
In-Reply-To: <20120824.124815.1292475998883382478.davem@davemloft.net>
On Fri, 2012-08-24 at 12:48 -0400, David Miller wrote:
> From: Ben Hutchings <bhutchings@solarflare.com>
> Date: Mon, 20 Aug 2012 22:16:51 +0100
>
> > This initialises the operstate synchronously at registration time
> > only.
>
> Ok, this looks good to me, applied. Thanks Ben.
>
> > This seems to deal properly with the registration-time problem, but not
> > the case where a device is brought down and then up again. Many but not
> > all drivers that support carrier detection call netif_carrier_off() in
> > their ndo_stop method. Should the others be changed, or is there some
> > way we can make that automatic?
>
> There are several cases.
>
> For example, if the device does not power down the PHY over stop/start
> it should leave the carrier state alone. This is the case for every
> NIC that runs management firmware, which therefore needs the link to
> stay up even when the NIC is administratively brought down.
>
> If it does power down the PHY, that netif_carrier_off() call should
> already be contained in the PHY powerdown code.
Right, that makes sense to me.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2012-08-24 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 21:16 [PATCH net-next] net: Set device operstate at registration time Ben Hutchings
2012-08-24 16:48 ` David Miller
2012-08-24 16:53 ` Ben Hutchings [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=1345827235.2694.12.camel@bwh-desktop.uk.solarflarecom.com \
--to=bhutchings@solarflare.com \
--cc=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=mike@marineau.org \
--cc=netdev@vger.kernel.org \
--cc=shchepetkov@ispras.ru \
--cc=shemminger@vyatta.com \
/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