From: Doug Ledford <dledford@redhat.com>
To: Arseny Maslennikov <ar@cs.msu.ru>, linux-rdma@vger.kernel.org
Cc: Jason Gunthorpe <jgg@ziepe.ca>, netdev@vger.kernel.org
Subject: Re: [PATCH v2 1/2] IB/ipoib: Use dev_port to expose network interface port numbers
Date: Thu, 30 Aug 2018 16:17:58 -0400 [thread overview]
Message-ID: <075a5d0f9fb9dfc868e82073f930a98bea15e578.camel@redhat.com> (raw)
In-Reply-To: <20180830182238.16361-2-ar@cs.msu.ru>
[-- Attachment #1: Type: text/plain, Size: 2112 bytes --]
On Thu, 2018-08-30 at 21:22 +0300, Arseny Maslennikov wrote:
> Some InfiniBand network devices have multiple ports on the same PCI
> function. This initializes the `dev_port' sysfs field of those
> network interfaces with their port number.
>
> Prior to this the kernel erroneously used the `dev_id' sysfs
> field of those network interfaces to convey the port number to userspace.
>
> The use of `dev_id' was considered correct until Linux 3.15,
> when another field, `dev_port', was defined for this particular
> purpose and `dev_id' was reserved for distinguishing stacked ifaces
> (e.g: VLANs) with the same hardware address as their parent device.
>
> Similar fixes to net/mlx4_en and many other drivers, which started
> exporting this information through `dev_id' before 3.15, were accepted
> into the kernel 4 years ago.
> See 76a066f2a2a0 (`net/mlx4_en: Expose port number through sysfs').
>
> Signed-off-by: Arseny Maslennikov <ar@cs.msu.ru>
> ---
> drivers/infiniband/ulp/ipoib/ipoib_main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/ulp/ipoib/ipoib_main.c b/drivers/infiniband/ulp/ipoib/ipoib_main.c
> index e3d28f9ad9c0..ba16a63ee303 100644
> --- a/drivers/infiniband/ulp/ipoib/ipoib_main.c
> +++ b/drivers/infiniband/ulp/ipoib/ipoib_main.c
> @@ -1880,7 +1880,7 @@ static int ipoib_parent_init(struct net_device *ndev)
> sizeof(union ib_gid));
>
> SET_NETDEV_DEV(priv->dev, priv->ca->dev.parent);
> - priv->dev->dev_id = priv->port - 1;
> + priv->dev->dev_port = priv->port - 1;
I don't know that we can't do this. At least not yet. Expose the new
item to make us compliant with the new docs, and deprecate the old sysfs
item, but we can't just yank the old item. Existing tools/scripts might
(probably) rely on it (existing tools already special case IPoIB
interfaces and we'll need to make sure they don't special case this
element too).
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-08-31 0:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 18:22 [PATCH v2 0/2] IB/ipoib: Use dev_port to disambiguate port numbers Arseny Maslennikov
2018-08-30 18:22 ` [PATCH v2 1/2] IB/ipoib: Use dev_port to expose network interface " Arseny Maslennikov
2018-08-30 20:17 ` Doug Ledford [this message]
2018-08-31 8:57 ` Arseny Maslennikov
2018-08-31 20:58 ` Doug Ledford
2018-08-30 18:22 ` [PATCH v2 2/2] Documentation/ABI: document /sys/class/net/*/dev_port Arseny Maslennikov
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=075a5d0f9fb9dfc868e82073f930a98bea15e578.camel@redhat.com \
--to=dledford@redhat.com \
--cc=ar@cs.msu.ru \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@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).