From: Tetsuya Mukawa <mukawa@igel.co.jp>
To: Linhaifeng <haifeng.lin@huawei.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] some questions about rte_memcpy
Date: Thu, 22 Jan 2015 19:23:49 +0900 [thread overview]
Message-ID: <54C0CFB5.909@igel.co.jp> (raw)
In-Reply-To: <20150122073526.GA14800@mhcomputing.net>
On 2015/01/22 16:35, Matthew Hall wrote:
> On Thu, Jan 22, 2015 at 01:32:04PM +0800, Linhaifeng wrote:
>> Do you mean if call rte_memcpy before rte_eal_init() would crash?why?
> No guarantee. But a theory. It might use some things from the EAL init to
> figure out which version of the accelerated algorithm to use.
This selection is done at compile-time.
And if the size is constant, I guess DPDK assumes memcpy is replaced by
inline __builtin_memcpy.
I haven't checked the performance of builtin memcpy, but probably much
faster.
Tetsuya
> Matthew.
next prev parent reply other threads:[~2015-01-22 10:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 3:39 Linhaifeng
2015-01-22 4:45 ` Matthew Hall
2015-01-22 5:32 ` Linhaifeng
2015-01-22 7:35 ` Matthew Hall
2015-01-22 10:23 ` Tetsuya Mukawa [this message]
2015-01-22 11:34 ` Bruce Richardson
2015-01-22 12:53 ` Linhaifeng
2015-01-22 15:21 ` Bruce Richardson
2015-01-23 2:58 ` Linhaifeng
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=54C0CFB5.909@igel.co.jp \
--to=mukawa@igel.co.jp \
--cc=dev@dpdk.org \
--cc=haifeng.lin@huawei.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).