DPDK usage discussions
 help / color / mirror / Atom feed
From: Lego Lin <lego.lin@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Memory consumption of struct rte_ring
Date: Mon, 17 Aug 2020 17:32:41 +0800	[thread overview]
Message-ID: <CALR1AzJTnq73U2k+6D9JKgDVt_jVrby8eT1ee8vOqk94Gyb0Pg@mail.gmail.com> (raw)

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

             reply	other threads:[~2020-08-17  9:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-17  9:32 Lego Lin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-08-14  3:02 Lego Lin

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=CALR1AzJTnq73U2k+6D9JKgDVt_jVrby8eT1ee8vOqk94Gyb0Pg@mail.gmail.com \
    --to=lego.lin@gmail.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).