From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "vadim.suraev@gmail.com" <vadim.suraev@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] rte_mbuf: mbuf bulk alloc/free functions added + unittest
Date: Tue, 17 Mar 2015 21:24:46 +0100 [thread overview]
Message-ID: <2117302.qM2478Su2B@xps13> (raw)
In-Reply-To: <1426623368-29748-1-git-send-email-vadim.suraev@gmail.com>
Hi Vadim,
It would be easier to track your changes if you were adding v2 and changelog.
Thanks
2015-03-17 22:16, vadim.suraev@gmail.com:
> From: "vadim.suraev@gmail.com" <vadim.suraev@gmail.com>
>
> - an API function to allocate a bulk of rte_mbufs
> - an API function to free a bulk of rte_mbufs
> - an API function to free a chained rte_mbuf
> - unittest for above
>
> Signed-off-by: vadim.suraev@gmail.com <vadim.suraev@gmail.com>
You should put your name before the email address.
> ---
> app/test/test_mbuf.c | 94 +++++++++++++++++++++++++++++++++++++++++++-
> lib/librte_mbuf/rte_mbuf.h | 89 +++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 182 insertions(+), 1 deletion(-)
prev parent reply other threads:[~2015-03-17 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 20:16 vadim.suraev
2015-03-17 20:24 ` Thomas Monjalon [this message]
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=2117302.qM2478Su2B@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=vadim.suraev@gmail.com \
/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).