From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.arccn.ru (vpn.arccn.ru [95.182.74.2]) by dpdk.org (Postfix) with SMTP id 913BB12A1 for ; Wed, 7 May 2014 09:54:35 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.arccn.ru (Postfix) with ESMTP id 1D56CA0092 for ; Wed, 7 May 2014 11:54:41 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=arccn.ru; h= content-transfer-encoding:content-type:content-type:in-reply-to :references:subject:subject:to:mime-version:user-agent:from:from :date:date:message-id; s=dkim; t=1399449263; x=1400313263; bh=Os Co4WIukUzHhf9tl1m1H0Te417yZWeuEKhSn5rKDsY=; b=sHachZHAIu1TVwurVV gsUxM0UCr0S9ML5nu1bOYG/88j+eT8l7XWZ/wk6Da2/w4O+ad1x038fTkN4bJqtE k/LYVDiCx/z1iu3MCslkFU8h6LLrAty2Om1ZcMStxyBVjjVHGFqpZtb6yA05fz99 T96rLr6aU+M+d1E4x9r+x0MHA= X-Virus-Scanned: Debian amavisd-new at mail.arccn.ru Received: from mail.arccn.ru ([127.0.0.1]) by localhost (mail.arccn.ru [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l-ULW6Z6Jr5m for ; Wed, 7 May 2014 11:54:23 +0400 (MSK) Received: from [10.30.40.100] (unknown [10.30.40.100]) by mail.arccn.ru (Postfix) with ESMTPSA id E39B2A0091 for ; Wed, 7 May 2014 11:54:23 +0400 (MSK) Message-ID: <5369E6AF.4040402@arccn.ru> Date: Wed, 07 May 2014 11:54:23 +0400 From: Igor Ryzhov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: dev@dpdk.org References: <5368A5E0.8090903@arccn.ru> In-Reply-To: <5368A5E0.8090903@arccn.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-dev] RTE Ring removing X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 May 2014 07:54:35 -0000 Hello again. I did some investigation on the code. I learned that RTE Ring creation function uses functions related to RTE=20 Memzone to reserve memory (rte_memzone_reserve). Documentation states that once reserved memzone can not be unreserved. I=20 decided to find out why it is so. I noticed that in Memzone realization there is a special global variable=20 "free_memseg" containing pointers on free memory segments. An memzone reserve function just finst the best segment for allocation=20 from this "free_memseg" variable. So I think there is a possibility to unreserve already reserved memory=20 back to "free_memseg", and impossibility of unreserving memory is just=20 because there is no function for that, not because it is impossible in=20 principle. Am I right? Or there are any restrictions? Best regards, Igor Ryzhov 06.05.2014 13:05, Igor Ryzhov =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > 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=20 > think there may be a problem with memory because of many ring that=20 > already not in use, but allocated. > Or DPDK has a mechanism of reusing memory if rings are not in use? > > Best regards, > Igor Ryzhov