mlx4_core: identify function as pf or vf
Subsystems (5)
PATCH v2 1/25 mlx4_core: identify function as pf or vf
From: Liran Liss <liranl-VPRAkNaXOzVS1MOuV/[email protected]>
--- include/linux/mlx4/device.h | 19 +++++++++++++++++++ 1 files changed, 19 insertions(+), 0 deletions(-)
include/linux/mlx4/device.h +19 -0
@@ -42,6 +42,9 @@enum {MLX4_FLAG_MSI_X =1 <<0 ,MLX4_FLAG_OLD_PORT_CMDS =1 <<1 , +MLX4_FLAG_MASTER =1 <<2 , +MLX4_FLAG_SLAVE =1 <<3 , +MLX4_FLAG_SRIOV =1 <<4 , };enum {
@@ -375,6 +378,7 @@ struct mlx4_av {struct mlx4_dev {struct pci_dev *pdev;unsigned long flags; +unsigned long num_slaves;struct mlx4_caps caps;struct radix_tree_root qp_table_tree;u32 rev_id;
@@ -400,6 +404,21 @@ struct mlx4_init_port_param {if (((type) ==MLX4_PORT_TYPE_IB ? (dev)->caps.port_mask : \ ~(dev)->caps.port_mask) &1 << ((port) -1 )) +static inline int mlx4_is_slave(struct mlx4_dev *dev) +{ +return dev->flags &MLX4_FLAG_SLAVE ; +} + +static inline int mlx4_is_master (struct mlx4_dev *dev) +{ +return dev->flags &MLX4_FLAG_MASTER ; +} + +static inline int mlx4_is_mfunc (struct mlx4_dev *dev) +{ +return dev->flags & (MLX4_FLAG_MASTER |MLX4_FLAG_SLAVE ); +} +int mlx4_buf_alloc (struct mlx4_dev *dev,int size,int max_direct,struct mlx4_buf *buf);void mlx4_buf_free (struct mlx4_dev *dev,int size,struct mlx4_buf *buf);
Signature · 9 lines
1.5.3.7 -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): 4AF3930E.90904-VPRAkNaXOzVS1MOuV/[email protected]
include/linux/mlx4/device.h line 48
Quoted 8 lines
enum {
include/linux/mlx4/device.h +3
-0MLX4_FLAG_MSI_X =1 <<0 ,MLX4_FLAG_OLD_PORT_CMDS =1 <<1 , +MLX4_FLAG_MASTER =1 <<2 , +MLX4_FLAG_SLAVE =1 <<3 , + MLX4_FLAG_SRIOV = 1 << 4, };
I'm a bit confused by these flags. As far as I can tell, the SRIOV flag will be set if and only if MASTER is set too... so in other words we might as well just have the MASTER and SLAVE flags and not have the SRIOV flag at all.
- R.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): adar5peouu3.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org
Quoted 2 lines
I'm a bit confused by these flags. As far as I can tell, the SRIOV flag will be set if and > only if MASTER is set too... so in other words we might as well just have the MASTER and > > SLAVE flags and not have the SRIOV flag at all.
We could have a situation where we have multiple physical functions, without SRIOV. In this case one of the functions would be MASTER, but not SRIOV
Yevgeny
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): E113D394D7C5DB4F8FF691FA7EE9DB44384E3CAC3F-WQlSmcKwN8Te+A/[email protected]
Quoted 5 lines
Quoted 2 lines
I'm a bit confused by these flags. As far as I can tell, the SRIOV flag will be set if and > only if MASTER is set too... so in other words we might as well just have the MASTER and > > SLAVE flags and not have the SRIOV flag at all.
We could have a situation where we have multiple physical functions, without SRIOV. In this case one of the functions would be MASTER, but not SRIOV
Where in the code could that happen? The only place I see the SRIOV or MASTER flag get set is a line like:
dev->flags |= MLX4_FLAG_SRIOV | MLX4_FLAG_MASTER;
so they are never used separately.
- R.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html