diff options
author | Alexander Duyck <alexander.h.duyck@intel.com> | 2013-09-28 06:00:22 +0000 |
---|---|---|
committer | Jeff Kirsher <jeffrey.t.kirsher@intel.com> | 2013-10-09 21:22:01 -0700 |
commit | fc4ac67bc98f1d54ec0ef8bcddf54892ad78e1f9 (patch) | |
tree | 502943f7a5a91496891e83f3348fd804e135506e /lib/mpi/mpi-bit.c | |
parent | 35a1e2ad1716fe3d956eea6e356ca2758f6392a7 (diff) |
i40e: Do not directly increment Tx next_to_use
Avoid directly incrementing next_to_use for multiple reasons. The main
reason being that if we directly increment it then it can attain a state
where it is equal to the ring count. Technically this is a state it
should not be able to reach but the way this is written it now can.
This patch pulls the value off into a register and then increments it
and writes back either the value or 0 depending on if the value is equal
to the ring count.
Signed-off-by: Alexander Duyck <alexander.h.duyck@intel.com>
Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
Tested-by: Kavindya Deegala <kavindya.s.deegala@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat (limited to 'lib/mpi/mpi-bit.c')
0 files changed, 0 insertions, 0 deletions