From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Qi Zhang <qi.z.zhang@intel.com>, dev@dpdk.org
Cc: gage.eads@intel.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] bus/vdev: fix wrong error log on secondary device scan
Date: Mon, 27 Aug 2018 17:16:28 +0100 [thread overview]
Message-ID: <7ea4dd19-cd84-7b40-e0b9-ff25b85d6769@intel.com> (raw)
In-Reply-To: <20180827122732.5531-1-qi.z.zhang@intel.com>
On 27-Aug-18 1:27 PM, Qi Zhang wrote:
> When a secondary process handles VDEV_SCAN_ONE mp action, it is possible
> the device is already be inserted. This happens when we have multiple
> secondary processes which cause multiple broadcasts from primary during
> bus->scan. So we don't need to log any error for -EEXIST.
>
> Bugzilla ID: 84
> Fixes: cdb068f031c6 ("bus/vdev: scan by multi-process channel")
> Cc: stable@dpdk.org
>
> Reported-by: Eads Gage <gage.eads@intel.com>
> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
> ---
> drivers/bus/vdev/vdev.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/bus/vdev/vdev.c b/drivers/bus/vdev/vdev.c
> index 6139dd551..af9526fe6 100644
> --- a/drivers/bus/vdev/vdev.c
> +++ b/drivers/bus/vdev/vdev.c
> @@ -346,6 +346,7 @@ vdev_action(const struct rte_mp_msg *mp_msg, const void *peer)
> const struct vdev_param *in = (const struct vdev_param *)mp_msg->param;
> const char *devname;
> int num;
> + int ret;
>
> strlcpy(mp_resp.name, VDEV_MP_KEY, sizeof(mp_resp.name));
> mp_resp.len_param = sizeof(*ou);
> @@ -380,7 +381,10 @@ vdev_action(const struct rte_mp_msg *mp_msg, const void *peer)
> break;
> case VDEV_SCAN_ONE:
> VDEV_LOG(INFO, "receive vdev, %s", in->name);
> - if (insert_vdev(in->name, NULL, NULL) < 0)
> + ret = insert_vdev(in->name, NULL, NULL);
> + if (ret == -EEXIST)
> + VDEV_LOG(INFO, "device already exist, %s", in->name);
This is probably going to be printed a lot, and there's no real point in
that. Maybe set log level to DEBUG instead?
> + else if (ret < 0)
> VDEV_LOG(ERR, "failed to add vdev, %s", in->name);
> break;
> default:
>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-08-27 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 12:27 Qi Zhang
2018-08-27 16:16 ` Burakov, Anatoly [this message]
2018-09-03 8:49 ` Qi Zhang
2018-09-03 8:50 ` [dpdk-dev] [PATCH v2] " Qi Zhang
2018-09-04 14:45 ` Eads, Gage
2018-09-16 9:35 ` Thomas Monjalon
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=7ea4dd19-cd84-7b40-e0b9-ff25b85d6769@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=gage.eads@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=stable@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).