From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jianbo Liu <jianbo.liu@linaro.org>
Cc: dev@dpdk.org, jerin.jacob@caviumnetworks.com
Subject: Re: [dpdk-dev] [PATCH] arm64: change rte_memcpy to inline function
Date: Fri, 13 May 2016 17:49:53 +0200 [thread overview]
Message-ID: <2364439.Jm7BSl6O9C@xps13> (raw)
In-Reply-To: <1462869064-9423-1-git-send-email-jianbo.liu@linaro.org>
2016-05-10 14:01, Jianbo Liu:
> Other APP may call rte_memcpy by function pointer,
> so change it to an inline function.
Any example in mind?
> --- a/lib/librte_eal/common/include/arch/arm/rte_memcpy_64.h
> +++ b/lib/librte_eal/common/include/arch/arm/rte_memcpy_64.h
> -#define rte_memcpy(d, s, n) memcpy((d), (s), (n))
> +static inline void *
> +rte_memcpy(void *dst, const void *src, size_t n)
> +{
> + return memcpy(dst, src, n);
> +}
It has no sense if other archs (arm32, ppc64, tile) are not updated.
next prev parent reply other threads:[~2016-05-13 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 8:31 Jianbo Liu
2016-05-13 9:12 ` Jerin Jacob
2016-05-13 15:49 ` Thomas Monjalon [this message]
2016-05-19 13:48 ` Jianbo Liu
2016-05-19 15:56 ` Thomas Monjalon
2016-06-17 10:30 ` Thomas Monjalon
2016-06-22 8:10 ` Jianbo Liu
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=2364439.Jm7BSl6O9C@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=jianbo.liu@linaro.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).