On Azure, increasing VF's gso/gro packet size to up-to GSO_MAX_SIZE
is not possible without allowing the same for netvsc NIC
(as the NICs are bonded together). For bonded NICs, the min of the max
aggregated pkt size of the members is propagated in the stack.
Therefore, we use netif_set_tso_max_siz
Allow the max aggregated pkt size to go up-to GSO_MAX_SIZE for MANA NIC.
This patch only increases the max allowable gso/gro pkt size for MANA
devices and does not change the defaults.
Following are the perf benefits by increasing the pkt aggregate size from
legacy gso_max_size value(64K) to newer
Allow the max gso/gro aggregated pkt size to go up to GSO_MAX_SIZE for
MANA NIC. On Azure, this not possible without allowing the same for
netvsc NIC (as the NICs are bonded together).
Therefore, we use netif_set_tso_max_size() to set max aggregated pkt size
to VF's tso_max_size for netvsc too, whe
On Fri, 07 Feb 2025 13:46:28 -0800, lon...@linuxonhyperv.com wrote:
> Ajay is no longer working on the MANA RDMA driver.
>
> Konstantin Taranov has made significant contributions to implementing RC
> QP in both kernel and user-mode.
>
> He will take the responsibility of fixing bugs, reviewing
On Fri, Feb 07, 2025 at 01:36:15PM -0800, lon...@linuxonhyperv.com wrote:
> From: Long Li
>
> When populating GID cache for net devices in a bonded setup, it should use
> the master device's
> address whenever applicable.
>
> The current code has some incorrect behaviors when dealing with bonde
