On 11/11/2022 9:12 AM, Matt wrote:
>
>
> On Thu, Nov 10, 2022 at 12:39 AM Stephen Hemminger
> mailto:step...@networkplumber.org>> wrote:
>
> On Wed, 9 Nov 2022 14:04:34 +0800
> Yangchao Zhou mailto:zhouya...@gmail.com>> wrote:
>
> > In some scenarios, mbufs returned by rte_kni_rx_b
On Thu, Nov 10, 2022 at 12:39 AM Stephen Hemminger <
step...@networkplumber.org> wrote:
> On Wed, 9 Nov 2022 14:04:34 +0800
> Yangchao Zhou wrote:
>
> > In some scenarios, mbufs returned by rte_kni_rx_burst are not freed
> > immediately. So kni_allocate_mbufs may be failed, but we don't know.
>
On Wed, 9 Nov 2022 14:04:34 +0800
Yangchao Zhou wrote:
> In some scenarios, mbufs returned by rte_kni_rx_burst are not freed
> immediately. So kni_allocate_mbufs may be failed, but we don't know.
>
> Even worse, when alloc_q is completely exhausted, kni_net_tx in
> rte_kni.ko will drop all tx p
In some scenarios, mbufs returned by rte_kni_rx_burst are not freed
immediately. So kni_allocate_mbufs may be failed, but we don't know.
Even worse, when alloc_q is completely exhausted, kni_net_tx in
rte_kni.ko will drop all tx packets. kni_allocate_mbufs is never
called again, even if the mbufs
4 matches
Mail list logo