From: Stephen Hemminger <stephen@networkplumber.org>
To: ola.liljedahl@arm.com, Thomas Monjalon <thomas@monjalon.net>
Cc: Honnappa.Nagarahalli@arm.com, bruce.richardson@intel.com,
dev@dpdk.org, gage.eads@intel.com, nd@arm.com,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Subject: Re: [RFC,v2] lfring: lock-free ring buffer
Date: Fri, 9 Jun 2023 10:10:09 -0700 [thread overview]
Message-ID: <20230609171009.83009-1-stephen@networkplumber.org> (raw)
In-Reply-To: <1548866179-20766-1-git-send-email-ola.liljedahl@arm.com>
This patch is old, and was covered by later ring changes.
It should be marked as superseded or rejected in patchwork
prev parent reply other threads:[~2023-06-09 17:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 16:36 [dpdk-dev] " Ola Liljedahl
2019-06-05 18:21 ` Eads, Gage
2019-06-15 21:00 ` Ola Liljedahl
2019-06-18 17:06 ` Eads, Gage
2023-06-09 17:10 ` Stephen Hemminger [this message]
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=20230609171009.83009-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=gage.eads@intel.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=nd@arm.com \
--cc=ola.liljedahl@arm.com \
--cc=thomas@monjalon.net \
/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).