Bug#946160: hwloc: please round PCIe link values

2019-12-04 Thread Brice Goglin
Le 04/12/2019 à 18:51, Laurent Bonnaud a écrit :
> On 04/12/2019 16.15, Brice Goglin wrote:
>
>> PCIe links (since Gen3) are encoded 128 data rate over 130 signal rate.
>> That's why you get 3.93 (truncated to 3.9). We decided to keep that
>> value exact in hwloc because the data/signal rate is different among
>> PCIe generations. We could round it up to 4 in the lstopo output, but I
>> am not sure where to start (PCIe Gen4 16x is 31.5GB/s instead of 32 and
>> Gen5 will be 63 instead of 64, those are harder to round up).
> Thanks for the detailed explanation!
>
> How about displaying the PCIe generation and number of links?


We often get similar requests for various hardware attributes.
Unfortunately, hwloc is not an exhaustive inventory tool. lstopo is the
visible part of a library for managing hardware locality. Adding many
somehow-unrelated hardware details might be risky (slow down the
discovery process, make the API larger, make the ABI harder to maintain,
etc).

We rather tell people to use dedicated tools for getting
hardware-specific details. In the case of PCI Gen + number of lanes,
there's a notion of "supported maximal" rate per lane and "current" rate
(high-end GPUs slowdown PCI lanes when idle). I'd rather not handle all
these details in hwloc.

Brice



Bug#946160: hwloc: please round PCIe link values

2019-12-04 Thread Laurent Bonnaud
On 04/12/2019 16.15, Brice Goglin wrote:

> PCIe links (since Gen3) are encoded 128 data rate over 130 signal rate.
> That's why you get 3.93 (truncated to 3.9). We decided to keep that
> value exact in hwloc because the data/signal rate is different among
> PCIe generations. We could round it up to 4 in the lstopo output, but I
> am not sure where to start (PCIe Gen4 16x is 31.5GB/s instead of 32 and
> Gen5 will be 63 instead of 64, those are harder to round up).

Thanks for the detailed explanation!

How about displaying the PCIe generation and number of links?

-- 
Laurent.



Bug#946160: hwloc: please round PCIe link values

2019-12-04 Thread Brice Goglin


Le 04/12/2019 à 15:30, Laurent Bonnaud a écrit :
> Package: hwloc
> Version: 2.1.0+dfsg-2
> Severity: normal
>
>
> Dear Maintainer,
>
> my system has a NVMe SSD.  It is displayed correctly in lstopo.  However the 
> PCIe link has a value of "3.9" (see attached file) whereas it should probably 
> be "4.0".


Hello

PCIe links (since Gen3) are encoded 128 data rate over 130 signal rate.
That's why you get 3.93 (truncated to 3.9). We decided to keep that
value exact in hwloc because the data/signal rate is different among
PCIe generations. We could round it up to 4 in the lstopo output, but I
am not sure where to start (PCIe Gen4 16x is 31.5GB/s instead of 32 and
Gen5 will be 63 instead of 64, those are harder to round up).

Brice



Bug#946160: hwloc: please round PCIe link values

2019-12-04 Thread Laurent Bonnaud
Package: hwloc
Version: 2.1.0+dfsg-2
Severity: normal


Dear Maintainer,

my system has a NVMe SSD.  It is displayed correctly in lstopo.  However the 
PCIe link has a value of "3.9" (see attached file) whereas it should probably 
be "4.0".


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAG>
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages hwloc depends on:
ii  libc6   2.29-4
ii  libcairo2   1.16.0-4
ii  libhwloc15  2.1.0+dfsg-2
ii  libtinfo6   6.1+20191019-1
ii  libx11-62:1.6.8-1

hwloc recommends no packages.

hwloc suggests no packages.

-- no debconf information

-- 
Laurent.


lstopo.pdf
Description: Adobe PDF document