63cfcf90fe
When we call update_max_size, it does not drop all oversized messages. This is due to the difficulty in performing this operation, since it is a FIFO which makes updating anything other than head or tail very difficult. To fix this, modify validate_msg_size to ensure that we error out later when trying to transmit the message that could be oversized. This will generally be a rare condition, as it requires the FIFO to include a message larger than the max_size negotiated during mailbox connect. Note that max_size is always smaller than rx.size, so it should be safe to use here. Also, update the update_max_size function header comment to clearly indicate that it does not drop all oversized messages, but only those at the head of the FIFO. Signed-off-by: Wang Xiao W <xiao.w.wang@intel.com> |
||
---|---|---|
.. | ||
fm10k_api.c | ||
fm10k_api.h | ||
fm10k_common.c | ||
fm10k_common.h | ||
fm10k_mbx.c | ||
fm10k_mbx.h | ||
fm10k_osdep.h | ||
fm10k_pf.c | ||
fm10k_pf.h | ||
fm10k_tlv.c | ||
fm10k_tlv.h | ||
fm10k_type.h | ||
fm10k_vf.c | ||
fm10k_vf.h |