From: "Nicolas de Pesloüan" <nicolas.2p.debian@gmail.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: "Jiri Pirko" <jpirko@redhat.com>,
"Michał Mirosław" <mirqus@gmail.com>,
netdev@vger.kernel.org, davem@davemloft.net,
eric.dumazet@gmail.com, shemminger@vyatta.com
Subject: Re: [patch net-next-2.6 1/2] net: allow to change carrier via sysfs
Date: Wed, 31 Aug 2011 22:31:44 +0200 [thread overview]
Message-ID: <4E5E9A30.1040105@gmail.com> (raw)
In-Reply-To: <1314821537.3274.24.camel@bwh-desktop>
Le 31/08/2011 22:12, Ben Hutchings a écrit :
> On Wed, 2011-08-31 at 22:03 +0200, Nicolas de Pesloüan wrote:
>> Le 31/08/2011 10:45, Jiri Pirko a écrit :
>>
>>>>>> Do you expect drivers using implementation different than just calling
>>>>>> netif_carrier_on/off? Or is it supposed to also e.g. power down PHYs?
>>>>> Yes, generally it can be used also for en/disable phy, for testing
>>>>> purposes if hw and driver would support it.
>>>>
>>>> I'd like to see this working for GRE tunnel devices (for keepalive
>>>> daemon to be able to indicate to routing daemons whether tunnel is
>>>> really working) - implementation would be identical to dummy's case.
>>>> Should I prepare a patch or can I leave it to you?
>>>
>>> Ok, I can include it to this patchset (I'm going to repost first patch
>>> anyway)
>>
>> Can't we assume that the dummy's case is the default behavior and
>> register this default
>> ndo_change_carrier callback for every device ?
>
> You have got to be joking. No device driver that has real link
> monitoring should use this implementation.
Well, why not? Arguably, this is probably not the feature one would use every day, but...
Testing a cluster reaction to a link down event would be easier if one doesn't need to unplug the
cable for the test. I understand that one can turn off the switch port (physical or virtual), but
echo 0 > /sys/class/net/eth0/carrier would be nice too.
Of course, I assume that netif_carrier_on and netif_carrier_off are only called on real link status
change. So the value written into /sys/class/net/eth0/carrier would stay until the link revert it,
due to a double status change (up-down-up or down-up-down). But I may miss totally this point.
Nicolas.
next prev parent reply other threads:[~2011-08-31 20:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 14:46 [patch net-next-2.6 0/2] net: allow to change carrier via sysfs Jiri Pirko
2011-08-30 14:46 ` [patch net-next-2.6 1/2] " Jiri Pirko
2011-08-30 15:14 ` Ben Hutchings
2011-08-30 15:19 ` Jiri Pirko
2011-08-30 18:11 ` Michał Mirosław
2011-08-30 18:25 ` Stephen Hemminger
2011-08-31 8:31 ` Jiri Pirko
2011-08-31 8:26 ` Jiri Pirko
2011-08-31 8:33 ` Michał Mirosław
2011-08-31 8:45 ` Jiri Pirko
2011-08-31 20:03 ` Nicolas de Pesloüan
2011-08-31 20:12 ` Ben Hutchings
2011-08-31 20:26 ` Jiri Pirko
2011-08-31 20:31 ` Nicolas de Pesloüan [this message]
2011-08-31 20:44 ` Ben Hutchings
2011-08-31 20:48 ` Ben Greear
2011-08-31 21:36 ` Ben Hutchings
2011-08-31 21:40 ` Stephen Hemminger
2011-09-01 5:46 ` Jiri Pirko
2011-08-31 21:49 ` Ben Greear
2011-09-01 5:44 ` Jiri Pirko
2011-08-30 14:46 ` [patch net-next-2.6 2/2] dummy: implement carrier change Jiri Pirko
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=4E5E9A30.1040105@gmail.com \
--to=nicolas.2p.debian@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jpirko@redhat.com \
--cc=mirqus@gmail.com \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).