ionic: Use cached VF attributes
Each time a VF attribute is set via iproute a call to get the VF
configuration is also made. This is currently problematic because for
each VF configuration call there are multiple commands sent to the
device. Unfortunately, this doesn't scale well. Fix this by reporting
the cached VF attributes.
The original change to query the device for getting the VF attributes
f16f5be310 ("ionic: Query FW when getting VF info via ndo_get_vf_config")
was made to remain consistent with device set VF attributes. However,
after further investigation there is no need to query the device.
Signed-off-by: Brett Creeley <brett.creeley@amd.com>
Signed-off-by: Shannon Nelson <shannon.nelson@amd.com>
Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
Reviewed-by: Rahul Rameshbabu <rrameshbabu@nvidia.com>
Link: https://lore.kernel.org/r/20231204210936.16587-2-shannon.nelson@amd.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
This commit is contained in:
committed by
Jakub Kicinski
parent
2f57dd94bd
commit
15e54faa5d
@@ -341,8 +341,7 @@ void ionic_dev_cmd_port_pause(struct ionic_dev *idev, u8 pause_type);
|
||||
|
||||
int ionic_set_vf_config(struct ionic *ionic, int vf,
|
||||
struct ionic_vf_setattr_cmd *vfc);
|
||||
int ionic_dev_cmd_vf_getattr(struct ionic *ionic, int vf, u8 attr,
|
||||
struct ionic_vf_getattr_comp *comp);
|
||||
|
||||
void ionic_dev_cmd_queue_identify(struct ionic_dev *idev,
|
||||
u16 lif_type, u8 qtype, u8 qver);
|
||||
void ionic_vf_start(struct ionic *ionic);
|
||||
|
||||
Reference in New Issue
Block a user