Sorry, I meant that "the mbufs will not be freed as the threshold for
freeing seems to not be based on the pool the mbuf originated from, but
based on the pool the PMD is configured to use"
On Tue, Apr 30, 2019 at 11:37 AM Paras Jha wrote:
> Hi,
>
> I think this issue seems to be due to how the
Hi,
I think this issue seems to be due to how the PMD frees mbufs. If the PMD
is configured with pool X, and KNI configured with pool Y, and pool Y has
far fewer mbufs available than pool X, when an application calls tx_burst
on the PMD, the mbufs will not be freed as the threshold for freeing see
On 4/10/2019 2:10 PM, Paras Jha wrote:
> Hi all,
>
> I've been chasing down a strange issue related to rte_kni_tx_burst.
>
> My application calls rte_kni_rx_burst, which allocates from a discrete mbuf
> pool using kni_allocate_mbufs. That traffic is immediately sent to
> rte_eth_tx_burst which do
Hi all,
I've been chasing down a strange issue related to rte_kni_tx_burst.
My application calls rte_kni_rx_burst, which allocates from a discrete mbuf
pool using kni_allocate_mbufs. That traffic is immediately sent to
rte_eth_tx_burst which does not seem to be freeing mbufs even upon
succesful c
4 matches
Mail list logo
