From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] mempool: don't leak ring on failure
Date: Tue, 24 Jun 2014 17:48:33 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB97725821334117@IRSMSX105.ger.corp.intel.com> (raw)
In-Reply-To: <20140624104057.1fa81fd6@nehalam.linuxnetplumber.net>
>
> On Tue, 24 Jun 2014 16:16:02 +0000
> "Ananyev, Konstantin" <konstantin.ananyev@intel.com> wrote:
>
> > But now, memzone created for the actual mempool could get leaked instead?
>
> Since memzone's can't be destroyed, then only solution would be if
> checked if memzone with same name already exists.
Actually, wouldn't it be the better way to create one memzone for both mempool and its ring?
Now we have rte_ring_init().
Konstantin
next prev parent reply other threads:[~2014-06-24 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 15:49 Stephen Hemminger
2014-06-24 16:16 ` Ananyev, Konstantin
2014-06-24 17:40 ` Stephen Hemminger
2014-06-24 17:48 ` Ananyev, Konstantin [this message]
2014-06-24 17:41 ` Richardson, Bruce
2014-06-25 7:46 ` Olivier MATZ
2014-06-25 8:01 ` Olivier MATZ
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=2601191342CEEE43887BDE71AB97725821334117@IRSMSX105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).