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 t
tation.
On Tue, Apr 30, 2019 at 10:59 AM Ferruh Yigit
wrote:
> 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 di
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
Hi all,
Are there any caveats with the usage of RTE_ETH_FOREACH_DEV? I have 4
interfaces bound to the igb_uio driver, but the macro seems to never
enumerate over any of them.
On another note, trying to manually specify a whitelist of devices to use
as a command line option always yields a message
4 matches
Mail list logo
