From: "Varghese, Vipin" <vipin.varghese@intel.com>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
"olivier.matz@6wind.com" <olivier.matz@6wind.com>,
"Pattan, Reshma" <reshma.pattan@intel.com>,
"Wiles, Keith" <keith.wiles@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Padubidri, Sanjay A" <sanjay.padubidri@intel.com>,
nd <nd@arm.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v1 1/2] lib/ring: add enqueue-dequeue callabck
Date: Mon, 10 Jun 2019 05:12:54 +0000 [thread overview]
Message-ID: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D366038@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <VE1PR08MB514984070E0FF53455C3328198100@VE1PR08MB5149.eurprd08.prod.outlook.com>
Hi Honnappa,
snipped
> >
> > Add callback event handler for enqueue dequeue operation on ring.
> > The pre-enqueue and post-dequeue operation on ring is selected to
> > invoke user callback handler.
> Can you provide a use case for this to better understand the need?
Use cases:
- allow user to investigate the contents pre-enqueue.
- allow user to investigate the contents post-dequeue.
- modify pre-enqueue and post-dequeue stage content.
- investigate PMD meta data for debug in field nodes.
snipped
> > + struct rte_ring_enq_cb_list enq_cbs;
> > + struct rte_ring_deq_cb_list deq_cbs; };
> This breaks ABI compatibility
Can you help me understand this more clearly?
snipped
> > -rte_ring_enqueue_burst(struct rte_ring *r, void * const *obj_table,
> > +rte_ring_enqueue_burst(struct rte_ring *r, void **obj_table,
> > unsigned int n, unsigned int *free_space) {
> > +#ifdef RTE_RING_ENQDEQ_CALLBACKS
> > + struct rte_ring_callback *cb = NULL;
> > +
> > + TAILQ_FOREACH(cb, &(r->enq_cbs), next) {
> Need to take the TAILQ lock before this. For ex: what happens if a un-register is
> called concurrently?
Let me check this, using rx|tx callback as reference.
> Also, traversing a linked list for every enqueue call would be too costly. May be,
> understanding the use case will help.
Internal testing with SP-SC is 0.1% (with extra cost of user function). But I will try to explore other alternatives too.
Snipped
next prev parent reply other threads:[~2019-06-10 5:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 18:33 Vipin Varghese
2019-06-06 18:33 ` [dpdk-dev] [PATCH v1 2/2] examples/packet_ordering: add ring callback Vipin Varghese
2019-06-06 19:49 ` [dpdk-dev] [PATCH v1 1/2] lib/ring: add enqueue-dequeue callabck Stephen Hemminger
2019-06-07 9:30 ` Bruce Richardson
2019-06-10 5:14 ` Varghese, Vipin
2019-06-07 10:45 ` Ananyev, Konstantin
2019-06-10 5:16 ` Varghese, Vipin
2019-06-10 5:07 ` Varghese, Vipin
2019-06-07 6:03 ` Honnappa Nagarahalli
2019-06-10 5:12 ` Varghese, Vipin [this message]
2019-06-11 4:17 ` Honnappa Nagarahalli
2019-07-04 5:04 ` Varghese, Vipin
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=4C9E0AB70F954A408CC4ADDBF0F8FA7D4D366038@BGSMSX101.gar.corp.intel.com \
--to=vipin.varghese@intel.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
--cc=nd@arm.com \
--cc=olivier.matz@6wind.com \
--cc=reshma.pattan@intel.com \
--cc=sanjay.padubidri@intel.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).