Hi Konstantin,
On 05/07/2014 05:19 PM, Ananyev, Konstantin wrote:
> Just to clarify about mempool - I suppose you are talking about
> ability to place internal ring and mempool metadata inside externally
> allocated memory?
Yes, exactly.
> It is already possible to keep mempool elements inside e
Hi Venky,
On 05/07/2014 04:01 PM, Venkatesan, Venky wrote:
> We should look at how to make the memseg capable of doing alloc/free
> (including re-assembly of fragments) after the 1.7 release. Is that
> something you are considering doing (or are there any other DPDKers
> considering this), or shou
It seems to be a good idea, thank you, Olivier!
But a few questions:
1. Will this changes affect performance?
2. In PATCH 2/2 you have a small bug:
In file rte_ring.h, in comments describing rte_ring_init function you have:
+ * @param name
+ * The size of the ring.
But it is name of the ring,
r that?
>
>Regards,
>-Venky
>
>-Original Message-
>From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Olivier MATZ
>Sent: Wednesday, May 07, 2014 4:39 AM
>To: Igor Ryzhov; dev at dpdk.org
>Subject: Re: [dpdk-dev] RTE Ring removing
>
>Hi Igor,
>
>On 05/07/2014 09
-Original Message-
From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Olivier MATZ
Sent: Wednesday, May 07, 2014 4:10 PM
To: Venkatesan, Venky; Igor Ryzhov; dev at dpdk.org
Subject: Re: [dpdk-dev] RTE Ring removing
Hi Venky,
On 05/07/2014 04:01 PM, Venkatesan, Venky wrote:
> We should look
Hi Igor,
On 05/07/2014 02:42 PM, Igor Ryzhov wrote:
> But a few questions:
> 1. Will this changes affect performance?
It should not. If you have many rings, you may allocate them
in huge pages to avoid TLB misses.
> 2. In PATCH 2/2 you have a small bug:
>
> In file rte_ring.h, in comments descri
?
Regards,
-Venky
-Original Message-
From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Olivier MATZ
Sent: Wednesday, May 07, 2014 4:39 AM
To: Igor Ryzhov; dev at dpdk.org
Subject: Re: [dpdk-dev] RTE Ring removing
Hi Igor,
On 05/07/2014 09:54 AM, Igor Ryzhov wrote:
> I noticed that
Hi Igor,
On 05/07/2014 09:54 AM, Igor Ryzhov wrote:
> 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.
>
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 i
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
10 matches
Mail list logo
