From: Stephen Hemminger <stephen@networkplumber.org>
To: Rory Sexton <rory.sexton@intel.com>
Cc: honnappa.nagarahalli@arm.com, konstantin.v.ananyev@yandex.ru,
dev@dpdk.org
Subject: Re: [RFC 1/1] ring: add infrastructure to allow callbacks within the ring library
Date: Tue, 31 Oct 2023 14:41:46 -0700 [thread overview]
Message-ID: <20231031144146.488ddc4a@fedora> (raw)
In-Reply-To: <20230323113743.4086730-2-rory.sexton@intel.com>
On Thu, 23 Mar 2023 11:37:43 +0000
Rory Sexton <rory.sexton@intel.com> wrote:
> From: Rory Sexton <rory.sexton@intel.com>
> To: honnappa.nagarahalli@arm.com, konstantin.v.ananyev@yandex.ru
> Cc: dev@dpdk.org, Rory Sexton <rory.sexton@intel.com>
> Subject: [RFC 1/1] ring: add infrastructure to allow callbacks within the ring library
> Date: Thu, 23 Mar 2023 11:37:43 +0000
> X-Mailer: git-send-email 2.34.1
>
> Adding initial code to give a feel for what it would look like if
> callbacks were supported by the ring dequeue functions within the
> ring library. They could be optionally compiled in/out as required.
>
> Signed-off-by: Rory Sexton <rory.sexton@intel.com>
Interesting but there is no current use for this.
Adding dead code, just creates more test cases and bloat to DPDK.
Could you use tracepoints for this instead.
next prev parent reply other threads:[~2023-10-31 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 11:37 [RFC 0/1] ring: add callback infrastructire to " 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 [this message]
2023-03-23 11:55 ` [RFC 0/1] ring: add callback infrastructire to " Morten Brørup
2023-04-05 0:46 ` 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=20231031144146.488ddc4a@fedora \
--to=stephen@networkplumber.org \
--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).