From: nisarg joshi <njnisarg@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Guidance about how to carry out flow control at L2
Date: Mon, 27 Jan 2020 19:16:18 +0530 [thread overview]
Message-ID: <CAG+ei2KR2Du85Nx6wkkWBn8yhRckfavrrs5ykOp44wgvAgyjWw@mail.gmail.com> (raw)
Hello community,
I am working on a project in ns-3(network simulator) where we have a
NetDevice implemented called "DpdkNetDevice" which emulates a net device
using dpdk. The traffic control module/layer having the qdisc is a part of
ns-3 and the transmit ring is a part of the dpdk environment. Both the
queues are not in sync and we want to implement flow control between these
2 queues. We have a mechanism where we can signal the tc qdisc to stop and
start, but for that, we require to know the empty space in the transmit
ring. Can you please help us out with the correct API we should be using?
Or is there some mechanism that dpdk has implemented for signaling the
upper layers from the transmit ring? We have come across a function called
rte_eth_tx_descriptor_status using which we are planning to check the
status of the tail to judge if there is empty space. Can you guys help us
in any way regarding this?
Thank you
Regards
reply other threads:[~2020-01-27 13:46 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=CAG+ei2KR2Du85Nx6wkkWBn8yhRckfavrrs5ykOp44wgvAgyjWw@mail.gmail.com \
--to=njnisarg@gmail.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).