From: "Kundapura, Ganapati" <ganapati.kundapura@intel.com>
To: dpdk-dev <dev@dpdk.org>, Jerin Jacob <jerinjacobk@gmail.com>,
"Jayatheerthan, Jay" <jay.jayatheerthan@intel.com>
Subject: [dpdk-dev] RFC: Enahancements to Rx adapter for DPDK 21.11
Date: Fri, 23 Jul 2021 07:02:42 +0000 [thread overview]
Message-ID: <CO1PR11MB4882A75BADD0412DFC5E104E87E59@CO1PR11MB4882.namprd11.prod.outlook.com> (raw)
Hi dpdk-dev,
We would like to submit series of patches to Rx adapters
that will enhance the configuration and performance.
Please find the details below.
(1) Configure Rx event buffer at run time
Add new api to configure the size of the Rx event buffer at run time.
This api allows setting the size of the event buffer at adapter level.
(2) Change packet enqueue buffer in Rx adapter to circular buffer
Rx adapter uses memmove() to move unprocessed events to the begining
of packet enqueue buffer which consumes good amount of CPU cycles.
(3) Add API to retrieve the Rx queue info
Rx queue info containining flags for handling received packets,
event queue identifier, schedular type, event priority,
polling frequence of the receive queue and flow identifier
(4) Add adapter_stats cli to retrive Rx/Tx adapter stats and rxq info
This cli displays Rx and Tx adapter stats containing recieved packet count,
eventdev enqueue count, enqueue retry count, event buffer size, queue poll count,
transmitted packet count, packet dropped count, transmit fail count etc and rx queue info.
(5) Update Rx timestamp in mbuf using mbuf dynamic field
Add support to register timestamp dynamic field in mbuf
Update the timestamp in mbuf for each packet before eventdev enqueue
We look forward to feedback on this proposal. Once we have initial feedback,
patches will be submitted for review.
Thanks,
Ganapati
next reply other threads:[~2021-07-23 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 7:02 Kundapura, Ganapati [this message]
2021-07-26 13:04 ` Kundapura, Ganapati
2021-07-28 6:08 ` Jerin Jacob
2021-07-28 6:23 ` Kundapura, Ganapati
2021-07-30 11:17 ` Jerin Jacob
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=CO1PR11MB4882A75BADD0412DFC5E104E87E59@CO1PR11MB4882.namprd11.prod.outlook.com \
--to=ganapati.kundapura@intel.com \
--cc=dev@dpdk.org \
--cc=jay.jayatheerthan@intel.com \
--cc=jerinjacobk@gmail.com \
/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).