From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Marc Sune <marc.sune@bisdn.de>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4] KNI: use a memzone pool for KNI alloc/release
Date: Tue, 21 Oct 2014 10:29:36 +0200 [thread overview]
Message-ID: <11046523.OQamTbecJT@xps13> (raw)
In-Reply-To: <1413586289-6694-1-git-send-email-marc.sune@bisdn.de>
Hi Marc,
2014-10-18 00:51, Marc Sune:
> This patch implements the KNI memzone pool in order to prevent
> memzone exhaustion when allocating/deallocating KNI interfaces.
>
> It adds a new API call, rte_kni_init(max_kni_ifaces) that shall
> be called before any call to rte_kni_alloc() if KNI is used.
>
> v2: Moved KNI fd opening to rte_kni_init(). Revised style.
> v3: Adapted kni examples/tests to rte_kni_init().
> v4: Improved example integration. Fixed kni_memzone_pool_alloc/release() bug.
>
> Signed-off-by: Marc Sune <marc.sune@bisdn.de>
Thanks for the good work with Helin.
Before applying this patch, I'd like another version explaining in the
commit log why this change is needed.
And please use to checkpatch.pl to check and remove whitespace errors.
Thanks
--
Thomas
next prev parent reply other threads:[~2014-10-21 8:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 22:51 Marc Sune
2014-10-21 4:57 ` Zhang, Helin
2014-10-21 8:29 ` Thomas Monjalon [this message]
2014-10-21 10:52 ` Marc Sune
2014-10-22 5:51 ` Liu, Jijiang
2014-10-22 7:10 ` [dpdk-dev] [PATCH] KNI: fix compilation warning 'missing-field-initializers' Marc Sune
2014-10-22 7:14 ` Marc Sune
2014-10-22 8:11 ` Liu, Jijiang
2014-10-22 8:37 ` Thomas Monjalon
2014-10-22 8:42 ` Marc Sune
2014-10-22 8:50 ` Thomas Monjalon
2014-10-22 9:49 ` Marc Sune
2014-10-22 9:59 ` Richardson, Bruce
2014-10-22 10:00 ` Thomas Monjalon
2014-10-22 10:23 ` [dpdk-dev] [PATCH v2] " Marc Sune
2014-10-22 10:35 ` Thomas Monjalon
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=11046523.OQamTbecJT@xps13 \
--to=thomas.monjalon@6wind.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).