From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: rusty@rustcorp.com.au, netdev@vger.kernel.org, mst@redhat.com,
izumi.taku@jp.fujitsu.com
Subject: Re: [PATCH] virtio_net: implements ethtool_ops.get_drvinfo
Date: Wed, 04 Aug 2010 21:54:24 -0700 (PDT) [thread overview]
Message-ID: <20100804.215424.200345652.davem@davemloft.net> (raw)
In-Reply-To: <1280980041.13192.628.camel@localhost>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Thu, 05 Aug 2010 04:47:21 +0100
> On Thu, 2010-08-05 at 13:02 +0930, Rusty Russell wrote:
>> I often use "ethtool -i" command to check what driver controls the
>> ehternet device. But because current virtio_net driver doesn't
>> support "ethtool -i", it becomes the following:
>>
>> # ethtool -i eth3
>> Cannot get driver information: Operation not supported
>>
>> This patch simply adds the "ethtool -i" support. The following is the
>> result when using the virtio_net driver with my patch applied to.
>>
>> # ethtool -i eth3
>> driver: virtio_net
>> version: N/A
>> firmware-version: N/A
>> bus-info: virtio0
>>
>> Personally, "-i" is one of the most frequently-used option, and most
>> network drivers support "ethtool -i", so I think virtio_net also
>> should do.
> [...]
>
> This information is already available generically through sysfs:
> basename $(readlink /sys/class/net/eth3/device)
> basename $(readlink /sys/class/net/eth3/device/driver)
>
> Given that, we should either recommend that people use that method
> instead, or we should add an equivalent default implementation of the
> get_drvinfo operation.
We've had ethtool for nearly a decade, it's a standard facility and
it's only wise to have all drivers implement as much of the API as
possible.
As such I've applied Rusty's patch and I will apply any patch which
makes a driver more fully provide support for all ethtool facilities.
next prev parent reply other threads:[~2010-08-05 4:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 3:32 [PATCH] virtio_net: implements ethtool_ops.get_drvinfo Rusty Russell
2010-08-05 3:47 ` Ben Hutchings
2010-08-05 4:54 ` David Miller [this message]
2010-08-05 19:20 ` [PATCH] ethtool: Provide a default implementation of ethtool_ops::get_drvinfo Ben Hutchings
2010-08-17 8:50 ` David Miller
2010-08-06 15:59 ` [PATCH] virtio_net: implements ethtool_ops.get_drvinfo Loke, Chetan
2010-08-06 16:15 ` Ben Hutchings
-- strict thread matches above, loose matches on Subject: below --
2010-06-11 1:29 Taku Izumi
2010-06-15 4:28 ` Rusty Russell
2010-06-15 5:20 ` Taku Izumi
2010-06-16 1:54 ` Rusty Russell
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=20100804.215424.200345652.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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).