Searched hist:e9031f2da1aef34b0b4c659ead613c335b46ae92 (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/drivers/net/ethernet/intel/i40e/ |
| H A D | i40e_txrx.h | diff e9031f2da1aef34b0b4c659ead613c335b46ae92 Thu Mar 09 12:56:13 CST 2023 Tirthendu Sarkar <tirthendu.sarkar@intel.com> i40e: introduce next_to_process to i40e_ring
Add a new field called next_to_process in the i40e_ring that is
advanced for every buffer and change the semantics of next_to_clean to
point to the first buffer of a packet. Driver will use next_to_process
in the same way next_to_clean was used previously.
For the non multi-buffer case, next_to_process and next_to_clean will
always be the same since each packet consists of a single buffer.
Signed-off-by: Tirthendu Sarkar <tirthendu.sarkar@intel.com>
Tested-by: Chandan Kumar Rout <chandanx.rout@intel.com> (A Contingent Worker at Intel)
Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
|
| H A D | i40e_txrx.c | diff e9031f2da1aef34b0b4c659ead613c335b46ae92 Thu Mar 09 12:56:13 CST 2023 Tirthendu Sarkar <tirthendu.sarkar@intel.com> i40e: introduce next_to_process to i40e_ring
Add a new field called next_to_process in the i40e_ring that is
advanced for every buffer and change the semantics of next_to_clean to
point to the first buffer of a packet. Driver will use next_to_process
in the same way next_to_clean was used previously.
For the non multi-buffer case, next_to_process and next_to_clean will
always be the same since each packet consists of a single buffer.
Signed-off-by: Tirthendu Sarkar <tirthendu.sarkar@intel.com>
Tested-by: Chandan Kumar Rout <chandanx.rout@intel.com> (A Contingent Worker at Intel)
Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
|