DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>
To: Marc Sune <marc.sune@bisdn.de>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] mempool deleting and cache_size
Date: Thu, 16 Apr 2015 10:26:04 +0100	[thread overview]
Message-ID: <552F802C.1040208@intel.com> (raw)
In-Reply-To: <552F7F46.7050000@bisdn.de>

On 16/04/2015 10:22, Marc Sune wrote:
>
>
> On 16/04/15 11:03, Gonzalez Monroy, Sergio wrote:
>> On 15/04/2015 20:24, Stephen Hemminger wrote:
>>> On Wed, 15 Apr 2015 20:15:18 +0100
>>> Zoltan Kiss <zoltan.kiss@linaro.org> wrote:
>>>
>>>> Hi,
>>>>
>>>> I have two questions regarding mempools:
>>>>
>>>> - the first is trivial: how do you delete them? Can you? I can't see a
>>>> function to do that, and none of the examples are doing such thing. 
>>>> When
>>>> exactly it get deleted?
>>> You can't delete them. They live in hugepage area and are persistent.
>>> Correctly written code looks for them by name and reuses existing pool
>>> if it is big enough.
>>>
>> FYI, I'm looking into such functionality and also delete/destroy 
>> mempools (although still no plan on implementation).
>>
>
> Also the memzones behind, or will be "lost/leaked" after a mempool 
> destruction?
>
> Marc
>
>> Sergio
>
Sorry, my bad.
I did mean to say 'delete/destroy memzones' :)

Sergio

  reply	other threads:[~2015-04-16  9:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15 19:15 Zoltan Kiss
2015-04-15 19:24 ` Stephen Hemminger
2015-04-16  9:03   ` Gonzalez Monroy, Sergio
2015-04-16  9:18     ` Gonzalez Monroy, Sergio
2015-04-16  9:33       ` Olivier MATZ
2015-04-16  9:22     ` Marc Sune
2015-04-16  9:26       ` Gonzalez Monroy, Sergio [this message]
2015-04-17  8:32         ` Marc Sune
2015-04-17 10:28 ` Zoltan Kiss

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=552F802C.1040208@intel.com \
    --to=sergio.gonzalez.monroy@intel.com \
    --cc=dev@dpdk.org \
    --cc=marc.sune@bisdn.de \
    /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).