DPDK usage discussions
 help / color / mirror / Atom feed
From: Andriy Berestovskyy <aber@semihalf.com>
To: "Javier Coleto Fernández" <javicoleto44@gmail.com>
Cc: "Wiles, Keith" <keith.wiles@intel.com>, users <users@dpdk.org>
Subject: Re: [dpdk-users] mbuf free cnt not decreasing
Date: Mon, 18 Apr 2016 17:57:51 +0200	[thread overview]
Message-ID: <CAOysbxqH+o9MRQQgj06rmHJdt4gKeYGWOVy-tueMPP+_CMBQOA@mail.gmail.com> (raw)
In-Reply-To: <CABbgvktqO_jWdJ3XtazYzhZRUj8-mBDUhAhuTCMZGa7LW0wsbQ@mail.gmail.com>

On Mon, Apr 18, 2016 at 5:34 PM, Javier Coleto Fernández
<javicoleto44@gmail.com> wrote:
> Basing on what you say, is that return value supposed to be less than 'n' in
> case the ring is filled up or do I have to check the ring size before
> calling rte_eth_tx_burst()?

You just have to check the return value and free the unsent mbufs.
Here is an example:

ret = rte_eth_tx_burst(port, queueid, m_table, n);
if (unlikely(ret < n)) {
    do {
        rte_pktmbuf_free(m_table[ret]);
    } while (++ret < n);
}


Regards,
Andiry

  reply	other threads:[~2016-04-18 15:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15  8:34 Javier Coleto Fernández
2016-04-15 13:01 ` Andriy Berestovskyy
2016-04-18  8:41   ` Javier Coleto Fernández
2016-04-18  9:21     ` Andriy Berestovskyy
2016-04-18 14:37       ` Wiles, Keith
2016-04-18 15:34         ` Javier Coleto Fernández
2016-04-18 15:57           ` Andriy Berestovskyy [this message]
2016-04-18 16:01             ` Javier Coleto Fernández
2016-04-18 16:13               ` Andriy Berestovskyy
2016-04-18 16:29                 ` Wiles, Keith
2016-04-18 16:41                   ` Javier Coleto Fernández
2016-04-18 16:44                     ` Wiles, Keith
2016-04-19 11:30                       ` Javier Coleto Fernández
2016-04-18 14:53     ` Ferruh Yigit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOysbxqH+o9MRQQgj06rmHJdt4gKeYGWOVy-tueMPP+_CMBQOA@mail.gmail.com \
    --to=aber@semihalf.com \
    --cc=javicoleto44@gmail.com \
    --cc=keith.wiles@intel.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).