From: David Miller <davem@davemloft.net>
To: shannon.nelson@oracle.com
Cc: netdev@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] ldmvsw: add vio version and remote-mac to ethtool info
Date: Wed, 21 Jun 2017 15:05:46 -0400 (EDT) [thread overview]
Message-ID: <20170621.150546.230947714652245325.davem@davemloft.net> (raw)
In-Reply-To: <1498061394-233018-2-git-send-email-shannon.nelson@oracle.com>
From: Shannon Nelson <shannon.nelson@oracle.com>
Date: Wed, 21 Jun 2017 09:09:53 -0700
> In the ethtool -i output print the vio version and the remote-mac
> of the ldom that the vif device is serving as this vif info is
> not exposed elsewhere. The remote-mac address is most useful for
> tracking which client ldom is being served by the vif.
>
> Orabug: 26316362
>
> Signed-off-by: Shannon Nelson <shannon.nelson@oracle.com>
Although less useful, it is exposed already via the kernel logs.
Also, this is not at all an appropriate place to expose this. The
"driver info" ethtool command is not a place to post per-connection
or per-link information.
Probably one of the IFLA_* netlink attributes would work best for
this. You could even use PHYS_PORT_ID for this, which gives you
32 bytes to work with.
next prev parent reply other threads:[~2017-06-21 19:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 16:09 [PATCH net-next 0/2] sunvnet: add to ethtool data Shannon Nelson
2017-06-21 16:09 ` [PATCH net-next 1/2] ldmvsw: add vio version and remote-mac to ethtool info Shannon Nelson
2017-06-21 19:05 ` David Miller [this message]
2017-06-21 20:59 ` Shannon Nelson
2017-06-21 21:27 ` David Miller
2017-06-21 16:09 ` [PATCH net-next 2/2] sunvnet: implement basic ethtool get_settings Shannon Nelson
2017-06-21 19:06 ` David Miller
2017-06-21 20:59 ` Shannon Nelson
2017-06-21 21:28 ` David Miller
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=20170621.150546.230947714652245325.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shannon.nelson@oracle.com \
--cc=sparclinux@vger.kernel.org \
/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).