From: "Walukiewicz, Miroslaw" <Miroslaw.Walukiewicz@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] determine number of free TX descriptors in DPDK transmit queue
Date: Mon, 30 Mar 2015 09:51:13 +0000 [thread overview]
Message-ID: <7C4248CAE043B144B1CD242D275626532FE81DC4@IRSMSX104.ger.corp.intel.com> (raw)
Hello,
Is there any method of determining the number free TX descriptor in specific TX queue?
I know that when transmit function is called with some number packets to send and then number returned by function is different than provided that means that queue is full.
This mechanism works good when we have packets that fits single DPDK descriptor (rte_mbuf).
But when we provide longer descriptors for example up to 64K-long packets with different size it is good to predict how much space is available in the transmit queue, because creating such longs packets Is expensive and the application could work much more effectively when such information would be provided.
Regards,
Mirek
reply other threads:[~2015-03-30 9:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7C4248CAE043B144B1CD242D275626532FE81DC4@IRSMSX104.ger.corp.intel.com \
--to=miroslaw.walukiewicz@intel.com \
--cc=dev@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).