From: "Li, Miao" <miao.li@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Xia, Chenbo" <chenbo.xia@intel.com>
Subject: RE: [PATCH v1] net/vhost: add queue status check
Date: Fri, 19 Nov 2021 06:30:30 +0000 [thread overview]
Message-ID: <CO1PR11MB49009CFCAD0A5198F12CC0ABEE9C9@CO1PR11MB4900.namprd11.prod.outlook.com> (raw)
In-Reply-To: <3b828df5-d2ee-44dd-0347-3ef975e2dd21@redhat.com>
Hi
> -----Original Message-----
> From: Maxime Coquelin <maxime.coquelin@redhat.com>
> Sent: Tuesday, November 16, 2021 5:36 PM
> To: Li, Miao <miao.li@intel.com>; dev@dpdk.org
> Cc: Xia, Chenbo <chenbo.xia@intel.com>
> Subject: Re: [PATCH v1] net/vhost: add queue status check
>
>
>
> On 11/16/21 10:34, Maxime Coquelin wrote:
> >
> >
> > On 11/16/21 17:44, Miao Li wrote:
> >> This patch adds queue status check to make sure that vhost monitor
> >> address will not be got until the link between backend and frontend
> > s/got/gone/?
> >> up and the packets are allowed to be queued.
> >
> > It needs a fixes tag.
If we don't add this check, rte_vhost_get_monitor_addr will return -EINVAL when check if dev is null. But before return, get_device() will be called and print error log "device not found". So we want to add this check and return -EINVAL before call rte_vhost_get_monitor_addr. If we don't add this check, the vhost monitor address will also not be got but vhost will print error log continuously. It have no function impact, so I think it is not a fix.
> >
> >> Signed-off-by: Miao Li <miao.li@intel.com>
> >> ---
> >> drivers/net/vhost/rte_eth_vhost.c | 2 ++
> >> 1 file changed, 2 insertions(+)
> >>
> >> diff --git a/drivers/net/vhost/rte_eth_vhost.c
> >> b/drivers/net/vhost/rte_eth_vhost.c
> >> index 070f0e6dfd..9d600054d8 100644
> >> --- a/drivers/net/vhost/rte_eth_vhost.c
> >> +++ b/drivers/net/vhost/rte_eth_vhost.c
> >> @@ -1415,6 +1415,8 @@ vhost_get_monitor_addr(void *rx_queue, struct
> >> rte_power_monitor_cond *pmc)
> >> int ret;
> >> if (vq == NULL)
> >> return -EINVAL;
> >> + if (unlikely(rte_atomic32_read(&vq->allow_queuing) == 0))
> >> + return -EINVAL;
>
> Also, EINVAL might not be the right return value here.
I don't know which return value will be better. Do you have any suggestions? Thanks!
>
> > How does it help?
> > What does prevent allow_queuing to become zero between the check and the
> > call to rte_vhost_get_monitor_addr?
This check will prevent vhost to print error log continuously.
> >
> > I think you need to implement the same logic as in eth_vhost_rx(), i.e.
> > check allow_queueing, set while_queueing, check allow_queueing, do your
> > stuff and clear while_queuing.
I think the while_queuing is unnecessary because we only read the value in vq and this API will only be called as a callback of RX.
Thanks,
Miao
> >
> >> ret = rte_vhost_get_monitor_addr(vq->vid, vq->virtqueue_id,
> >> &vhost_pmc);
> >> if (ret < 0)
> >>
> >
> > Maxime
next prev parent reply other threads:[~2021-11-19 6:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 16:44 Miao Li
2021-11-16 9:34 ` Maxime Coquelin
2021-11-16 9:36 ` Maxime Coquelin
2021-11-19 6:30 ` Li, Miao [this message]
2022-01-31 8:36 ` Maxime Coquelin
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=CO1PR11MB49009CFCAD0A5198F12CC0ABEE9C9@CO1PR11MB4900.namprd11.prod.outlook.com \
--to=miao.li@intel.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).