DPDK patches and discussions
 help / color / mirror / Atom feed
From: "lihuisong (C)" <lihuisong@huawei.com>
To: Stephen Hemminger <stephen@networkplumber.org>, <dev@dpdk.org>
Subject: Re: [PATCH 2/3] examples/l2fwd-keepalive: don't use EAL logtype
Date: Tue, 12 Dec 2023 19:53:02 +0800	[thread overview]
Message-ID: <583cbed5-5bd4-ab4b-64d9-7438fded310d@huawei.com> (raw)
In-Reply-To: <20231211172437.61958-3-stephen@networkplumber.org>

Acked-by: Huisong Li <lihuisong@huawei.com>

在 2023/12/12 1:23, Stephen Hemminger 写道:
> EAL logtype should be reserved for EAL library.
> This example is already using printf() so just print
> errors to stderr.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
>   examples/l2fwd-keepalive/shm.c | 21 +++++++--------------
>   1 file changed, 7 insertions(+), 14 deletions(-)
>
> diff --git a/examples/l2fwd-keepalive/shm.c b/examples/l2fwd-keepalive/shm.c
> index 7c7a9ea8ea3c..cbeeb511ef07 100644
> --- a/examples/l2fwd-keepalive/shm.c
> +++ b/examples/l2fwd-keepalive/shm.c
> @@ -5,7 +5,6 @@
>   #include <time.h>
>   
>   #include <rte_common.h>
> -#include <rte_log.h>
>   #include <rte_keepalive.h>
>   
>   #include "shm.h"
> @@ -28,28 +27,23 @@ struct rte_keepalive_shm *rte_keepalive_shm_create(void)
>   	fd = shm_open(RTE_KEEPALIVE_SHM_NAME,
>   		O_CREAT | O_TRUNC | O_RDWR, 0666);
>   	if (fd < 0)
> -		RTE_LOG(INFO, EAL,
> -			"Failed to open %s as SHM (%s)\n",
> -			RTE_KEEPALIVE_SHM_NAME,
> -			strerror(errno));
> +		fprintf(stderr, "Failed to open %s as SHM (%s)\n",
> +			RTE_KEEPALIVE_SHM_NAME, strerror(errno));
>   	else if (ftruncate(fd, sizeof(struct rte_keepalive_shm)) != 0)
> -		RTE_LOG(INFO, EAL,
> -			"Failed to resize SHM (%s)\n", strerror(errno));
> +		fprintf(stderr, "Failed to resize SHM (%s)\n", strerror(errno));
>   	else {
>   		ka_shm = (struct rte_keepalive_shm *) mmap(
>   			0, sizeof(struct rte_keepalive_shm),
>   			PROT_READ | PROT_WRITE,	MAP_SHARED, fd, 0);
>   		close(fd);
>   		if (ka_shm == MAP_FAILED)
> -			RTE_LOG(INFO, EAL,
> -				"Failed to mmap SHM (%s)\n", strerror(errno));
> +			fprintf(stderr, "Failed to mmap SHM (%s)\n", strerror(errno));
>   		else {
>   			memset(ka_shm, 0, sizeof(struct rte_keepalive_shm));
>   
>   			/* Initialize the semaphores for IPC/SHM use */
>   			if (sem_init(&ka_shm->core_died, 1, 0) != 0) {
> -				RTE_LOG(INFO, EAL,
> -					"Failed to setup SHM semaphore (%s)\n",
> +				fprintf(stderr, "Failed to setup SHM semaphore (%s)\n",
>   					strerror(errno));
>   				munmap(ka_shm,
>   					sizeof(struct rte_keepalive_shm));
> @@ -87,7 +81,7 @@ void rte_keepalive_relayed_state(struct rte_keepalive_shm *shm,
>   		 * ka_agent is not active.
>   		 */
>   		if (sem_getvalue(&shm->core_died, &count) == -1) {
> -			RTE_LOG(INFO, EAL, "Semaphore check failed(%s)\n",
> +			fprintf(stderr, "Semaphore check failed(%s)\n",
>   				strerror(errno));
>   			return;
>   		}
> @@ -95,8 +89,7 @@ void rte_keepalive_relayed_state(struct rte_keepalive_shm *shm,
>   			return;
>   
>   		if (sem_post(&shm->core_died) != 0)
> -			RTE_LOG(INFO, EAL,
> -				"Failed to increment semaphore (%s)\n",
> +			fprintf(stderr, "Failed to increment semaphore (%s)\n",
>   				strerror(errno));
>   	}
>   }

  reply	other threads:[~2023-12-12 11:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11 17:23 [PATCH 0/3] replace use of " Stephen Hemminger
2023-12-11 17:23 ` [PATCH 1/3] testpmd: replace EAL logtype with fprintf Stephen Hemminger
2023-12-12 11:51   ` lihuisong (C)
2023-12-11 17:23 ` [PATCH 2/3] examples/l2fwd-keepalive: don't use EAL logtype Stephen Hemminger
2023-12-12 11:53   ` lihuisong (C) [this message]
2023-12-11 17:23 ` [PATCH 3/3] examples/vm_power_manager: do not " Stephen Hemminger
2023-12-12 11:24   ` Hunt, David
2023-12-12 11:53   ` lihuisong (C)
2023-12-11 19:19 ` [PATCH 0/3] replace use of " Tyler Retzlaff
2023-12-11 20:15   ` Stephen Hemminger
2023-12-12  8:01   ` David Marchand
2024-02-16  3:36 ` [PATCH v2 0/3] replace use of EAL logtype in applications Stephen Hemminger
2024-02-16  3:36   ` [PATCH v2 1/3] examples/l2fwd-keepalive: don't use EAL logtype Stephen Hemminger
2024-02-16  8:04     ` Morten Brørup
2024-02-16  3:36   ` [PATCH v2 2/3] examples/vm_power_manager: do not " Stephen Hemminger
2024-02-16  3:36   ` [PATCH v2 3/3] testpmd: replace EAL logtype TESTPMD_LOG Stephen Hemminger
2024-03-08 13:35     ` Singh, Aman Deep
2024-03-08 16:26       ` Stephen Hemminger
2024-02-18  3:16   ` [PATCH v2 0/3] replace use of EAL logtype in applications fengchengwen
2024-03-08 18:10 ` [PATCH v3 " Stephen Hemminger
2024-03-08 18:10   ` [PATCH v3 1/3] examples/l2fwd-keepalive: don't use EAL logtype Stephen Hemminger
2024-03-08 18:10   ` [PATCH v3 2/3] examples/vm_power_manager: do not " Stephen Hemminger
2024-03-08 18:10   ` [PATCH v3 3/3] testpmd: replace EAL logtype TESTPMD_LOG Stephen Hemminger
2024-03-08 22:33 ` [PATCH v4 0/3] replace use of EAL logtype in applications Stephen Hemminger
2024-03-08 22:33   ` [PATCH v4 1/3] examples/l2fwd-keepalive: don't use EAL logtype Stephen Hemminger
2024-03-08 22:33   ` [PATCH v4 2/3] examples/vm_power_manager: do not " Stephen Hemminger
2024-03-08 22:33   ` [PATCH v4 3/3] testpmd: replace EAL logtype TESTPMD_LOG Stephen Hemminger
2024-03-11 10:24     ` Singh, Aman Deep

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=583cbed5-5bd4-ab4b-64d9-7438fded310d@huawei.com \
    --to=lihuisong@huawei.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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).