From: "jiangheng (G)" <jiangheng14@huawei.com>
To: "olivier.matz@6wind.com" <olivier.matz@6wind.com>,
"andrew.rybchenko@oktetlabs.ru" <andrew.rybchenko@oktetlabs.ru>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: rte_mempool_ops support "ring_sp_sc" in single thread mode
Date: Thu, 13 Jul 2023 04:12:12 +0000 [thread overview]
Message-ID: <e2743445d690447ba305bf33402ba020@huawei.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
Hi,
Whether rte_mempool_ops need supports the scenario where the producer and consumer are in the same thread?
Currently, "ring_sp_sc" can be used in this scenario, but its dequeue and enqueue functions have memory barriers, which are not required in the same single thread.
In addition, the number of r.prod and r.cons keeps increasing, and the recently released mbuf cannot be reused, which also affects the performance. If the cache is not enabled.
we can refer to mempool cache to implement "ring_single_thread_sp_sc". In this simple scenario, the performance should be improved.
This scenario is common:
Such as mbuf mempool. dpdk NICs receives a packet, the protocol stack processes and releases the packet. The alloc and release of the mbuf are in the same thread.
If it makes sense, I can offer a patch
Thanks
[-- Attachment #2: Type: text/html, Size: 3574 bytes --]
reply other threads:[~2023-07-13 4:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e2743445d690447ba305bf33402ba020@huawei.com \
--to=jiangheng14@huawei.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=olivier.matz@6wind.com \
--cc=users@dpdk.org \
/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).