Soft Patch Panel
 help / color / mirror / Atom feed
From: x-fn-spp@sl.ntt-tx.co.jp
To: ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Cc: spp@dpdk.org
Subject: [spp] [PATCH] spp_vf: fix to generate debug information
Date: Thu, 27 Dec 2018 18:04:00 +0900	[thread overview]
Message-ID: <201812270904.wBR940SU024668@imss04.silk.ntt-tx.co.jp> (raw)

From: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>

This patch changes 'inline' declaration to 'static inline'or 'extern
inline' to be able to generate debug information.

Signed-off-by: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
Signed-off-by: Naoki Takada <takada.naoki@lab.ntt.co.jp>
---
 src/vf/common/command_dec.c   | 4 ++--
 src/vf/common/spp_port.c      | 6 +++---
 src/vf/common/string_buffer.c | 4 ++--
 3 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/src/vf/common/command_dec.c b/src/vf/common/command_dec.c
index 5b6ffcf..b328ca8 100644
--- a/src/vf/common/command_dec.c
+++ b/src/vf/common/command_dec.c
@@ -212,7 +212,7 @@ spp_convert_component_type(const char *type_str)
 }
 
 /* set decode error */
-inline int
+static inline int
 set_decode_error(struct spp_command_decode_error *error,
 		const int error_code, const char *error_name)
 {
@@ -225,7 +225,7 @@ set_decode_error(struct spp_command_decode_error *error,
 }
 
 /* set decode error */
-inline int
+static inline int
 set_string_value_decode_error(struct spp_command_decode_error *error,
 		const char *value, const char *error_name)
 {
diff --git a/src/vf/common/spp_port.c b/src/vf/common/spp_port.c
index d7d374e..fd76d79 100644
--- a/src/vf/common/spp_port.c
+++ b/src/vf/common/spp_port.c
@@ -57,7 +57,7 @@ spp_port_ability_init(void)
 }
 
 /* Get information of port ability. */
-inline void
+extern inline void
 spp_port_ability_get_info(
 		int port_id, enum spp_port_rxtx rxtx,
 		struct spp_port_ability **info)
@@ -365,7 +365,7 @@ port_ability_each_operation(uint16_t port_id,
 }
 
 /* Wrapper function for rte_eth_rx_burst(). */
-inline uint16_t
+extern inline uint16_t
 spp_eth_rx_burst(
 		uint16_t port_id, uint16_t queue_id  __attribute__ ((unused)),
 		struct rte_mbuf **rx_pkts, const uint16_t nb_pkts)
@@ -387,7 +387,7 @@ spp_eth_rx_burst(
 }
 
 /* Wrapper function for rte_eth_tx_burst(). */
-inline uint16_t
+extern inline uint16_t
 spp_eth_tx_burst(
 		uint16_t port_id, uint16_t queue_id  __attribute__ ((unused)),
 		struct rte_mbuf **tx_pkts, uint16_t nb_pkts)
diff --git a/src/vf/common/string_buffer.c b/src/vf/common/string_buffer.c
index acf0f81..768dd3a 100644
--- a/src/vf/common/string_buffer.c
+++ b/src/vf/common/string_buffer.c
@@ -13,14 +13,14 @@
 #define RTE_LOGTYPE_SPP_STRING_BUFF RTE_LOGTYPE_USER1
 
 /* get message buffer capacity */
-inline size_t
+static inline size_t
 strbuf_get_capacity(const char *strbuf)
 {
 	return *((const size_t *)(strbuf - sizeof(size_t)));
 }
 
 /* re-allocate message buffer */
-inline char*
+static inline char*
 strbuf_reallocate(char *strbuf, size_t required_len)
 {
 	size_t new_cap = strbuf_get_capacity(strbuf) * 2;
-- 
2.17.1

             reply	other threads:[~2018-12-27  9:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-27  9:04 x-fn-spp [this message]
2018-12-28  4:26 ` Yasufumi Ogawa

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=201812270904.wBR940SU024668@imss04.silk.ntt-tx.co.jp \
    --to=x-fn-spp@sl.ntt-tx.co.jp \
    --cc=ferruh.yigit@intel.com \
    --cc=ogawa.yasufumi@lab.ntt.co.jp \
    --cc=spp@dpdk.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).