diff options
| author | Sagi Grimberg <sagi@grimberg.me> | 2018-11-01 19:13:12 +0300 |
|---|---|---|
| committer | Jason Gunthorpe <jgg@mellanox.com> | 2018-11-09 00:22:53 +0300 |
| commit | 9afc97c29b032af9a4112c2f4a02d5313b4dc71f (patch) | |
| tree | 09652d268caedca53404804c4f7ab2c1ec52ea64 /drivers/crypto | |
| parent | ce1fd6bfb15da135158e93a0ee4c0540cd26b43c (diff) | |
| download | linux-9afc97c29b032af9a4112c2f4a02d5313b4dc71f.tar.xz | |
mlx5: remove support for ib_get_vector_affinity
Devices that does not use managed affinity can not export a vector
affinity as the consumer relies on having a static mapping it can map to
upper layer affinity (e.g. sw queues). If the driver allows the user to
set the device irq affinity, then the affinitization of a long term
existing entites is not relevant.
For example, nvme-rdma controllers queue-irq affinitization is determined
at init time so if the irq affinity changes over time, we are no longer
aligned.
Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
Acked-by: Leon Romanovsky <leonro@mellanox.com>
Signed-off-by: Doug Ledford <dledford@redhat.com>
Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
Diffstat (limited to 'drivers/crypto')
0 files changed, 0 insertions, 0 deletions