diff options
author | Frederic Barrat <fbarrat@linux.vnet.ibm.com> | 2018-01-23 12:31:40 +0100 |
---|---|---|
committer | Michael Ellerman <mpe@ellerman.id.au> | 2018-01-24 11:42:57 +1100 |
commit | 2cb3d64b26984703a6bb80e66adcc3727ad37f9f (patch) | |
tree | 60e6328bbe1f183dc87704366a1723cc1d81f34f /drivers | |
parent | 6914c757118e2a60ba826d9959ccf5532779781b (diff) | |
download | linux-stable-2cb3d64b26984703a6bb80e66adcc3727ad37f9f.tar.gz linux-stable-2cb3d64b26984703a6bb80e66adcc3727ad37f9f.tar.bz2 linux-stable-2cb3d64b26984703a6bb80e66adcc3727ad37f9f.zip |
powerpc/powernv: Capture actag information for the device
In the opencapi protocol, host memory contexts are referenced by a
'actag'. During setup, a driver must tell the device how many actags
it can used, and what values are acceptable.
On POWER9, the NPU can handle 64 actags per link, so they must be
shared between all the PCI functions of the link. To get a global
picture of how many actags are used by each AFU of every function, we
capture some data at the end of PCI enumeration, so that actags can be
shared fairly if needed.
This is not powernv specific per say, but rather a consequence of the
opencapi configuration specification being quite general. The number
of available actags on POWER9 makes it more likely to be hit. This is
somewhat mitigated by the fact that existing AFUs are coded by
requesting a reasonable count of actags and existing devices carry
only one AFU.
Signed-off-by: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions