> This introduced additional check in Rx path, not sure what is the performance > impact. > > I can see Long already acked the v3, I just want to double check. > If Tx queue number > Rx queue number is not a common usecase, perhaps it can > be an option to forbid it instead of getting performance hit. > Or it can be possible to have a dedicated Rx queue, like queue_id 0, for Tx > completion events for Tx queue_id > Rx queue number, etc.. > > But Long if you prefer to continue with this patch, please ack it and I can > continue > with it.
Ferruh, thank you for raising this concern. We will run some tests to evaluate performance impact of this patch. Will update soon. Long
