Commit a158aeaf authored by Jacob Keller's avatar Jacob Keller Committed by Jeff Kirsher

i40e: update comment explaining where FDIR buffers are freed

The original comment implies that the only location where the raw_packet
buffer will be freed is in i40e_clean_tx_ring() which is incorrect. In
fact this isn't even the normal case. Update the comment explaining
where the memory is freed.

Change-ID: Ie0defc35ed1c3af183f81fdc60b6d783707a5595
Signed-off-by: default avatarJacob Keller <jacob.e.keller@intel.com>
Tested-by: default avatarAndrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: default avatarJeff Kirsher <jeffrey.t.kirsher@intel.com>
parent 9b37c937
...@@ -432,7 +432,12 @@ int i40e_add_del_fdir(struct i40e_vsi *vsi, ...@@ -432,7 +432,12 @@ int i40e_add_del_fdir(struct i40e_vsi *vsi,
ret = -EINVAL; ret = -EINVAL;
} }
/* The buffer allocated here is freed by the i40e_clean_tx_ring() */ /* The buffer allocated here will be normally be freed by
* i40e_clean_fdir_tx_irq() as it reclaims resources after transmit
* completion. In the event of an error adding the buffer to the FDIR
* ring, it will immediately be freed. It may also be freed by
* i40e_clean_tx_ring() when closing the VSI.
*/
return ret; return ret;
} }
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment