From: Tetsuya Mukawa <mukawa-AlSX/UN32fvPDbFq/vQRIQ@public.gmane.org>
To: Linhaifeng <haifeng.lin-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: 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-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org>
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 some questions about rte_memcpy Linhaifeng
[not found] ` <54C070DF.1050006-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-01-22 4:45 ` Matthew Hall
[not found] ` <20150122044531.GA13230-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org>
2015-01-22 5:32 ` Linhaifeng
[not found] ` <54C08B54.50700-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-01-22 7:35 ` Matthew Hall
[not found] ` <20150122073526.GA14800-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org>
2015-01-22 10:23 ` Tetsuya Mukawa [this message]
[not found] ` <54C0CFB5.909-AlSX/UN32fvPDbFq/vQRIQ@public.gmane.org>
2015-01-22 11:34 ` Bruce Richardson
2015-01-22 12:53 ` Linhaifeng
[not found] ` <54C0F2B9.7050006-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
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-alsx/un32fvpdbfq/vqriq@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=haifeng.lin-hv44wF8Li93QT0dZR+AlfA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.