From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Rory Sexton" <rory.sexton@intel.com>,
<honnappa.nagarahalli@arm.com>, <konstantin.v.ananyev@yandex.ru>
Cc: <dev@dpdk.org>
Subject: RE: [RFC 0/1] ring: add callback infrastructire to ring library
Date: Thu, 23 Mar 2023 12:55:23 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D877FF@smartserver.smartshare.dk> (raw)
In-Reply-To: <20230323113743.4086730-1-rory.sexton@intel.com>
> From: Rory Sexton [mailto:rory.sexton@intel.com]
> Sent: Thursday, 23 March 2023 12.38
>
> This is an RFC proposing the addition of a callback infrastructure to the ring
> library, particularly in the ring dequeue functions, but they could also be
> added to the enqueue functions if desired.
>
> Callbacks in the ring dequeue functions would be beneficial for a number of
> reasons including but not limited to the following:
> - would allow users to register specific functions to be called on dequeue of
> a
> ring avoiding the need to call the function within application code on
> several
> threads reading from said ring.
> - would mirror the callback functionality offered by the ethdev library for
> threads that read exclusively from a ring and process packets based off
> that,
> thus allowing for the same threads to read from either a NIC i/f or directly
> from a ring without needing a different codepath.
>
> The addition of callbacks wouldn't impact the reading of rings by more than 1
> cycle when no callbacks are registered. They could also additionally be
> compiled
> in/out as desired to give more confidence in maintaining performance when
> callbacks are not required.
On the condition that they can be omitted at build time, as you mention here, I don't mind having more callbacks.
>
> This RFC is to give a feel for what the additional APIs would be and how they
> would be integrated within the ring dequeue functions. As such only function
> declarations are present. If there is a willingness within the community to
> add
> callback infrastructure to the ring library I will implement further code.
I like the idea that these callbacks mimic the ethdev callbacks, so if proceeding with this, I think that both enqueue and dequeue callbacks should be added. The ethdev callbacks share one RTE_ETHDEV_RXTX_CALLBACKS define, so the ring callbacks can probably do the same.
>
> Rory Sexton (1):
> ring: add infrastructure to allow callbacks within the ring library
>
> lib/ring/rte_ring.h | 133 ++++++++++++++++++++++++++++++++++++++-
> lib/ring/rte_ring_core.h | 3 +
> 2 files changed, 135 insertions(+), 1 deletion(-)
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-03-23 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 11:37 Rory Sexton
2023-03-23 11:37 ` [RFC 1/1] ring: add infrastructure to allow callbacks within the " Rory Sexton
2023-10-31 21:41 ` Stephen Hemminger
2023-03-23 11:55 ` Morten Brørup [this message]
2023-04-05 0:46 ` [RFC 0/1] ring: add callback infrastructire to " Honnappa Nagarahalli
2023-04-05 14:44 ` Sexton, Rory
2023-04-05 15:49 ` Honnappa Nagarahalli
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=98CBD80474FA8B44BF855DF32C47DC35D877FF@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=rory.sexton@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).