Don't inline string functions
PATCH 1/1 Don't inline string functions
It makes no sense to inline string functions, in fact snprintf can't be inlined because the function supports variable number of arguments.
---
Resend because of lack of response
lib/librte_eal/bsdapp/eal/Makefile | 1 lib/librte_eal/common/eal_common_string_fns.c | 96 +++++++++++++++++++++++++ lib/librte_eal/common/include/rte_string_fns.h | 57 +------------- lib/librte_eal/linuxapp/eal/Makefile | 1 4 files changed, 102 insertions(+), 53 deletions(-)
lib/librte_eal/bsdapp/eal/Makefile +1 -0
@@ -67,6 +67,7 @@ SRCS-$(CONFIG_RTE_LIBRTE_EAL_BSDAPP) += SRCS-$(CONFIG_RTE_LIBRTE_EAL_BSDAPP) += eal_common_tailqs.c SRCS-$(CONFIG_RTE_LIBRTE_EAL_BSDAPP) += eal_common_errno.c SRCS-$(CONFIG_RTE_LIBRTE_EAL_BSDAPP) += eal_common_cpuflags.c +SRCS-$(CONFIG_RTE_LIBRTE_EAL_BSDAPP) += eal_common_string_fns.c SRCS-$(CONFIG_RTE_LIBRTE_EAL_BSDAPP) += eal_common_hexdump.c SRCS-$(CONFIG_RTE_LIBRTE_EAL_BSDAPP) += eal_common_devargs.c SRCS-$(CONFIG_RTE_LIBRTE_EAL_BSDAPP) += eal_common_vdev.c
lib/librte_eal/common/eal_common_string_fns.c new file +96 -0
96 lines not on this page · raw message
lib/librte_eal/common/include/rte_string_fns.h +4 -53
71 lines not on this page · raw message
lib/librte_eal/linuxapp/eal/Makefile +1 -0
@@ -75,6 +75,7 @@ SRCS-$(CONFIG_RTE_LIBRTE_EAL_LINUXAPP) + SRCS-$(CONFIG_RTE_LIBRTE_EAL_LINUXAPP) += eal_common_tailqs.c SRCS-$(CONFIG_RTE_LIBRTE_EAL_LINUXAPP) += eal_common_errno.c SRCS-$(CONFIG_RTE_LIBRTE_EAL_LINUXAPP) += eal_common_cpuflags.c +SRCS-$(CONFIG_RTE_LIBRTE_EAL_LINUXAPP) += eal_common_string_fns.c SRCS-$(CONFIG_RTE_LIBRTE_EAL_LINUXAPP) += eal_common_hexdump.c SRCS-$(CONFIG_RTE_LIBRTE_EAL_LINUXAPP) += eal_common_devargs.c SRCS-$(CONFIG_RTE_LIBRTE_EAL_LINUXAPP) += eal_common_vdev.c
A message that is not in the archive (sent off-list or not yet received): 20140514081932.37847146-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org
Richardson, Bruce
Acked-byQuoted 11 lines
-----Original Message-----
From: dev [mailto:[email protected]] On Behalf Of Stephen Hemminger
Sent: Wednesday, May 14, 2014 4:20 PM
To: [email protected]
Subject: [dpdk-dev] [PATCH] Don't inline string functionsIt makes no sense to inline string functions, in fact snprintf can't be inlined because the function supports variable number of arguments.
Signed-off-by Stephen Hemminger <[email protected]>
2014-05-14 08:19, Stephen Hemminger:
Quoted 8 lines
It makes no sense to inline string functions, in fact snprintf can't be inlined because the function supports variable number of arguments.
Signed-off-by Stephen Hemminger <[email protected]>---
Resend because of lack of response
Please do not resend patches. I prefer a ping request in the original thread.
By the way, you didn't take into account my first comments:
http://dpdk.org/ml/archives/dev/2014-April/002028.html and I'm still waiting answers to these patches: http://dpdk.org/ml/archives/dev/2014-March/001673.html http://dpdk.org/ml/archives/dev/2014-March/001676.html
PS: I was going to apply your patches with these fixes:
add FILE argument to debug functions
[Thomas: fix quota_watermark example]
eal: dont inline string functions
[Thomas: update includes]
Signature · 1 line
Thomas
Quoted 7 lines · On Wed, 14 May 2014 17:47:01 +0200 Thomas Monjalon…
2014-05-14 08:19, Stephen Hemminger:
Quoted 6 lines
It makes no sense to inline string functions, in fact snprintf can't be inlined because the function supports variable number of arguments.
Signed-off-by Stephen Hemminger <[email protected]>
Quoted 7 lines
Quoted 2 lines
---
Resend because of lack of responsePlease do not resend patches. I prefer a ping request in the original thread.
By the way, you didn't take into account my first comments:
http://dpdk.org/ml/archives/dev/2014-April/002028.html
All the issues there are changed. includes, copyright etc.
Quoted 2 lines
and I'm still waiting answers to these patches:
http://dpdk.org/ml/archives/dev/2014-March/001673.html
This is in the rte_sched group. patch 1
Quoted 1 line
http://dpdk.org/ml/archives/dev/2014-March/001676.html
This is more of a mess than want to get into right now. header conflicts are nuisance.