Use lmtst burst when more than 15 pointers is requested
to be freed.
Signed-off-by: Ashwin Sekhar T K
---
drivers/common/cnxk/roc_npa.h | 86 +++
1 file changed, 68 insertions(+), 18 deletions(-)
diff --git a/drivers/common/cnxk/roc_npa.h b/drivers/common/cnxk/ro
From: Jerin Jacob
Based on device support and use-case need, there are two different ways
to enable PFC. The first case is the port level PFC configuration, in
this case, rte_eth_dev_priority_flow_ctrl_set() API shall be used to
configure the PFC, and PFC frames will be generated using based on V
On Mon, Nov 29, 2021 at 8:24 PM Jerin Jacob wrote:
>
> On Sun, Nov 28, 2021 at 5:07 PM Jerin Jacob wrote:
> >
> > On Sun, Nov 28, 2021 at 5:01 PM Ori Kam wrote:
> > >
> > > Good for me
> > >
> > > Please send the meeting invite.
>
>
> Thanks, Ori, Thomas, and Ferruh for attending the meeting.
>
On Sat, 4 Dec 2021 22:54:58 +0530
wrote:
> + /**
> + * Maximum supported traffic class as per PFC (802.1Qbb) specification.
> + *
> + * Based on device support and use-case need, there are two different
> + * ways to enable PFC. The first case is the port level PFC
> +
The csum FWD mode parses any received packet to set mbuf offloads for the
transmitting burst, mainly in the checksum/TSO areas.
In the case of a tunnel header, the csum FWD tries to detect known tunnels
by the standard definition using the header'sdata and fallback to check the
packet type in the m
When kni driver calls eth_kni_start to start device, some fields such as
min_mtu and max_mtu of rte_kni_conf are not initialized. It will cause
kni_ioctl_create create a kni netdevice with a random min_mtu and max_mtu
value. This is unexpected and in some time we could not change the kni device
When kni driver calls eth_kni_start to start device, some fields such as
min_mtu and max_mtu of rte_kni_conf are not initialized. It will cause
kni_ioctl_create create a kni netdevice with a random min_mtu and max_mtu
value. This isunexpected and in some time we could not change the kni
device mtu
When kni driver calls eth_kni_start to start device, some fields such as
min_mtu and max_mtu of rte_kni_conf are not initialized. It will cause
kni_ioctl_create create a kni netdevice with a random min_mtu and max_mtu
value. This isunexpected and in some time we could not change the kni
device mtu
On Sat, Dec 4, 2021 at 11:08 PM Stephen Hemminger
wrote:
>
> On Sat, 4 Dec 2021 22:54:58 +0530
> wrote:
>
> > + /**
> > + * Maximum supported traffic class as per PFC (802.1Qbb)
> > specification.
> > + *
> > + * Based on device support and use-case need, there are two differe
9 matches
Mail list logo