From: Igor Ryzhov <iryzhov@arccn.ru>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] RTE Ring removing
Date: Wed, 07 May 2014 11:54:23 +0400 [thread overview]
Message-ID: <5369E6AF.4040402@arccn.ru> (raw)
In-Reply-To: <5368A5E0.8090903@arccn.ru>
Hello again.
I did some investigation on the code.
I learned that RTE Ring creation function uses functions related to RTE
Memzone to reserve memory (rte_memzone_reserve).
Documentation states that once reserved memzone can not be unreserved. I
decided to find out why it is so.
I noticed that in Memzone realization there is a special global variable
"free_memseg" containing pointers on free memory segments.
An memzone reserve function just finst the best segment for allocation
from this "free_memseg" variable.
So I think there is a possibility to unreserve already reserved memory
back to "free_memseg", and impossibility of unreserving memory is just
because there is no function for that, not because it is impossible in
principle.
Am I right? Or there are any restrictions?
Best regards,
Igor Ryzhov
06.05.2014 13:05, Igor Ryzhov пишет:
> Hello.
>
> For what reason RTE Rings can not be removed once created?
> In my application I want to use many rings with different names so I
> think there may be a problem with memory because of many ring that
> already not in use, but allocated.
> Or DPDK has a mechanism of reusing memory if rings are not in use?
>
> Best regards,
> Igor Ryzhov
next prev parent reply other threads:[~2014-05-07 7:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 9:05 Igor Ryzhov
2014-05-07 7:54 ` Igor Ryzhov [this message]
2014-05-07 11:39 ` Olivier MATZ
2014-05-07 12:42 ` Igor Ryzhov
2014-05-07 13:08 ` Olivier MATZ
2014-05-07 14:01 ` Venkatesan, Venky
2014-05-07 15:09 ` Olivier MATZ
2014-05-07 15:19 ` Ananyev, Konstantin
2014-05-07 15:37 ` Olivier MATZ
2014-05-07 15:36 ` Rogers, Gerald
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=5369E6AF.4040402@arccn.ru \
--to=iryzhov@arccn.ru \
--cc=dev@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).