On 10/19/2021 11:56 AM, Michal Krawczyk wrote:
PMD shouldn't advertise the same offloads as both per-queue and per-port [1]. Each offload capability should go either to the [rt]x_queue_offload_capa or [rt]x_offload_capa.
This is not exactly true. It is expected that queue offloads advertised as part of port offloads too. The logic is, if any offload can be applied in queue granularity it can be applied to all queues which becomes port offload. In document: Port capabilities = per-queue capabilities + pure per-port capabilities. There is a difference between "pure per-port capability" and "port capability", this may be source of the confusion. Since driver doesn't support queue specific offloads, code is not wrong, I will remove above paragraph and merge the patch, if you have objection or change request, please let me know, I can update in next-net.
As ENA currently doesn't support offloads which could be configured per-queue, only per-port flags should be set. In addition, to make the code cleaner, parsing appropriate offload flags is encapsulated into helper functions, in a similar matter it's done by the other PMDs. [1] https://doc.dpdk.org/guides/prog_guide/ poll_mode_drv.html?highlight=offloads#hardware-offload Fixes: 7369f88f88c0 ("net/ena: convert to new Rx offloads API") Fixes: 56b8b9b7e5d2 ("net/ena: convert to new Tx offloads API") Cc: sta...@dpdk.org Signed-off-by: Michal Krawczyk <m...@semihalf.com> Reviewed-by: Igor Chauskin <igo...@amazon.com> Reviewed-by: Shai Brandes <shaib...@amazon.com>
<...>
