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 v4 0/3] IB/ipoib: Use dev_port to disambiguate port numbers
Date: Thu, 13 Sep 2018 12:50:00 -0400 [thread overview]
Message-ID: <5568f0883a4c8a6e09f566ffc17b74b2bee8f4fe.camel@redhat.com> (raw)
In-Reply-To: <20180906145112.29245-1-ar@cs.msu.ru>
[-- Attachment #1: Type: text/plain, Size: 2027 bytes --]
On Thu, 2018-09-06 at 17:51 +0300, Arseny Maslennikov wrote:
> Pre-3.15 userspace had trouble distinguishing different ports
> of a NIC on a single PCI bus/device/function. To solve this,
> a sysfs field `dev_port' was introduced quite a while ago
> (commit v3.14-rc3-739-g3f85944fe207), and some relevant device
> drivers were fixed to use it, but not in case of IPoIB.
>
> The convention for some reason never got documented in the kernel, but
> was immediately adopted by userspace (notably udev[1][2], biosdevname[3])
>
> 1/3 documents the sysfs field — that's why I'm CC-ing netdev.
>
> This series was tested on and applies to 4.19-rc2.
>
> [1] https://lists.freedesktop.org/archives/systemd-devel/2014-June/020788.html
> [2] https://lists.freedesktop.org/archives/systemd-devel/2014-July/020804.html
> [3] https://github.com/CloudAutomationNTools/biosdevname/blob/c795d51dd93a5309652f0d635f12a3ecfabfaa72/src/eths.c#L38
>
> v1->v2: replace a line instead of inserting and then removing.
> v2->v3: restore both attributes, output a notice of deprecation to kmsg.
> v3->v4: style adjustments, join the deprecation notice to single line.
>
> Arseny Maslennikov (3):
> Documentation/ABI: document /sys/class/net/*/dev_port
> IB/ipoib: Use dev_port to expose network interface port numbers
> IB/ipoib: Log sysfs 'dev_id' accesses from userspace
>
> Documentation/ABI/testing/sysfs-class-net | 18 +++++++++++++
> drivers/infiniband/ulp/ipoib/ipoib_main.c | 33 +++++++++++++++++++++++
> 2 files changed, 51 insertions(+)
>
Series applied to for-next. But I think we should watch feedback from
people, and if people think the notification about using the wrong
variable is too noisy, then we might want to revert it or modify it to
only print out once per specific executable instead of once per run of
each executable.
--
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 --]
prev parent reply other threads:[~2018-09-13 22:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 14:51 [PATCH v4 0/3] IB/ipoib: Use dev_port to disambiguate port numbers Arseny Maslennikov
2018-09-06 14:51 ` [PATCH v4 1/3] Documentation/ABI: document /sys/class/net/*/dev_port Arseny Maslennikov
2018-09-06 14:51 ` [PATCH v4 2/3] IB/ipoib: Use dev_port to expose network interface port numbers Arseny Maslennikov
2018-09-06 14:51 ` [PATCH v4 3/3] IB/ipoib: Log sysfs 'dev_id' accesses from userspace Arseny Maslennikov
2018-09-07 15:43 ` Jason Gunthorpe
2018-09-07 17:14 ` Doug Ledford
2018-09-07 17:24 ` Jason Gunthorpe
2018-09-09 18:11 ` Arseny Maslennikov
2018-09-09 20:55 ` Arseny Maslennikov
2018-09-13 15:45 ` Doug Ledford
2018-09-13 16:50 ` Doug Ledford [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=5568f0883a4c8a6e09f566ffc17b74b2bee8f4fe.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).