From: David Marchand <david.marchand@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev <dev@dpdk.org>, "Xia, Chenbo" <chenbo.xia@intel.com>
Subject: Re: [PATCH 3/7] vhost: improve socket layer logs
Date: Tue, 4 Jan 2022 16:02:41 +0100 [thread overview]
Message-ID: <CAJFAV8wKhg01_b2qcQo12PWVYc3JwABFcasS_37wB+0HYYCixg@mail.gmail.com> (raw)
In-Reply-To: <20211223083659.245766-4-maxime.coquelin@redhat.com>
On Thu, Dec 23, 2021 at 9:37 AM Maxime Coquelin
<maxime.coquelin@redhat.com> wrote:
> @@ -471,16 +468,14 @@ vhost_user_client_reconnect(void *arg __rte_unused)
> sizeof(reconn->un));
> if (ret == -2) {
> close(reconn->fd);
> - VHOST_LOG_CONFIG(ERR,
> - "reconnection for fd %d failed\n",
> - reconn->fd);
> + VHOST_LOG_CONFIG(ERR, "(%s) reconnection for fd %d failed\n",
> + reconn->vsocket->path, reconn->fd);
> goto remove_fd;
> }
> if (ret == -1)
> continue;
>
> - VHOST_LOG_CONFIG(INFO,
> - "%s: connected\n", reconn->vsocket->path);
> + VHOST_LOG_CONFIG(INFO, "%s: connected\n", reconn->vsocket->path);
Another nit that I caught when testing in OVS.
For consistency, we can have () around the socket path.
dpdk|WARN|VHOST_CONFIG: (/var/lib/vhost_sockets/vhost0) failed to
connect: No such file or directory
dpdk|INFO|VHOST_CONFIG: (/var/lib/vhost_sockets/vhost0) reconnecting...
dpdk|INFO|VHOST_CONFIG: /var/lib/vhost_sockets/vhost4: connected
dpdk|INFO|VHOST_CONFIG: (/var/lib/vhost_sockets/vhost4) new device, handle is 0
dpdk|INFO|VHOST_CONFIG: /var/lib/vhost_sockets/vhost5: connected
dpdk|INFO|VHOST_CONFIG: (/var/lib/vhost_sockets/vhost5) new device, handle is 1
dpdk|INFO|VHOST_CONFIG: /var/lib/vhost_sockets/vhost6: connected
dpdk|INFO|VHOST_CONFIG: (/var/lib/vhost_sockets/vhost6) new device, handle is 2
dpdk|INFO|VHOST_CONFIG: /var/lib/vhost_sockets/vhost7: connected
dpdk|INFO|VHOST_CONFIG: (/var/lib/vhost_sockets/vhost7) new device, handle is 3
> vhost_user_add_connection(reconn->fd, reconn->vsocket);
> remove_fd:
> TAILQ_REMOVE(&reconn_list.head, reconn, next);
--
David Marchand
next prev parent reply other threads:[~2022-01-04 15:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-23 8:36 [PATCH 0/7] vhost: improve logging Maxime Coquelin
2021-12-23 8:36 ` [PATCH 1/7] vhost: improve IOTLB logs Maxime Coquelin
2022-01-04 14:44 ` David Marchand
2022-01-25 9:39 ` Maxime Coquelin
2021-12-23 8:36 ` [PATCH 2/7] vhost: improve vDPA registration failure log Maxime Coquelin
2021-12-23 8:36 ` [PATCH 3/7] vhost: improve socket layer logs Maxime Coquelin
2022-01-04 14:47 ` David Marchand
2022-01-25 10:44 ` Maxime Coquelin
2022-01-04 15:02 ` David Marchand [this message]
2022-01-25 10:50 ` Maxime Coquelin
2021-12-23 8:36 ` [PATCH 4/7] vhost: improve Vhost " Maxime Coquelin
2022-01-04 14:48 ` David Marchand
2022-01-25 10:50 ` Maxime Coquelin
2021-12-23 8:36 ` [PATCH 5/7] vhost: improve Vhost-user " Maxime Coquelin
2021-12-23 8:36 ` [PATCH 6/7] vhost: improve Virtio-net " Maxime Coquelin
2021-12-23 8:36 ` [PATCH 7/7] vhost: remove multi-line logs Maxime Coquelin
2021-12-23 15:59 ` [PATCH 0/7] vhost: improve logging Stephen Hemminger
2022-01-04 15:05 ` David Marchand
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=CAJFAV8wKhg01_b2qcQo12PWVYc3JwABFcasS_37wB+0HYYCixg@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
/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).