* [dpdk-users] Memory consumption of struct rte_ring
@ 2020-08-17 9:32 Lego Lin
0 siblings, 0 replies; 2+ messages in thread
From: Lego Lin @ 2020-08-17 9:32 UTC (permalink / raw)
To: users
Hi, everyone:
I am new for DPDK. Recently, I leveraged the DPDK library to address some
performance issues.
1. rte_ring
2. rte_rwlock_t
I have some questions
1. For rte_ring, what is the exact memory consumption?
Example: I want create a rte_ring with size = 512K
struct rte_ring * myring = rte_ring_create("My_test", 512*1024,
SOCKET_ANY, MP_SC)
Before I enqueue anything into ring, what is the exact memory
consumption of myring?
2. rte_rwlock_t
Will rte_rwlock_t guarantee memory barrier? It looks like only protect
data from thread accessing.
Thanks
^ permalink raw reply [flat|nested] 2+ messages in thread
* [dpdk-users] Memory consumption of struct rte_ring
@ 2020-08-14 3:02 Lego Lin
0 siblings, 0 replies; 2+ messages in thread
From: Lego Lin @ 2020-08-14 3:02 UTC (permalink / raw)
To: users
Hi, everyone:
I am new for DPDK. Recently, I leveraged the DPDK library to address some
performance issues.
1. rte_ring
2. rte_rwlock_t
I have some questions
1. For rte_ring, what is the exact memory consumption?
Example: I want create a rte_ring with size = 512K
struct rte_ring * myring = rte_ring_create("My_test", 512*1024,
SOCKET_ANY, MP_SC)
Before I enqueue anything into ring, what is the exact memory
consumption of myring?
2. rte_rwlock_t
Will rte_rwlock_t guarantee memory barrier? It looks like only protect
data from thread accessing.
Thanks
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-08-25 23:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-17 9:32 [dpdk-users] Memory consumption of struct rte_ring Lego Lin
-- strict thread matches above, loose matches on Subject: below --
2020-08-14 3:02 Lego Lin
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).