linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Hillf Danton <hdanton@sina.com>
Cc: mst <mst@redhat.com>, Eli Cohen <elic@nvidia.com>,
	virtualization <virtualization@lists.linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] vdpa: mlx5: prevent cvq work from hogging CPU
Date: Tue, 22 Mar 2022 09:59:14 +0800	[thread overview]
Message-ID: <CACGkMEt-PRCsBQ+EJVGeWGikJfLk-0M1dRPMqnp9YC5R4HYAjQ@mail.gmail.com> (raw)
In-Reply-To: <20220321123420.3207-1-hdanton@sina.com>

On Mon, Mar 21, 2022 at 8:34 PM Hillf Danton <hdanton@sina.com> wrote:
>
> On Mon, 21 Mar 2022 17:00:09 +0800 Jason Wang wrote:
> >
> > Ok, speak too fast.
>
> Frankly I have fun running faster five days a week.

:)

>
> > So you meant to add a cond_resched() in the loop?
>
> Yes, it is one liner.

Yes, there will be no "infinite" loop, but since the loop is triggered
by userspace. It looks to me it will delay the flush/drain of the
workqueue forever which is still suboptimal.

Thanks

>
> Hillf
>


  parent reply	other threads:[~2022-03-22  1:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21  6:04 [PATCH 1/2] vdpa: mlx5: prevent cvq work from hogging CPU Jason Wang
2022-03-21  6:04 ` [PATCH 2/2] vdpa: mlx5: synchronize driver status with CVQ Jason Wang
2022-03-21  6:56   ` Eli Cohen
2022-03-21  7:23   ` Michael S. Tsirkin
2022-03-21  7:36     ` Jason Wang
2022-03-21  6:31 ` [PATCH 1/2] vdpa: mlx5: prevent cvq work from hogging CPU Eli Cohen
2022-03-21  7:20 ` Michael S. Tsirkin
2022-03-21  7:35   ` Jason Wang
     [not found] ` <20220321085317.3148-1-hdanton@sina.com>
2022-03-21  8:59   ` Jason Wang
2022-03-21  9:00     ` Jason Wang
     [not found]       ` <20220321123420.3207-1-hdanton@sina.com>
2022-03-22  1:59         ` Jason Wang [this message]
     [not found]           ` <20220324005345.3623-1-hdanton@sina.com>
2022-03-24  2:34             ` Jason Wang
     [not found]             ` <20220324060419.3682-1-hdanton@sina.com>
2022-03-24  6:17               ` Michael S. Tsirkin
2022-03-24  8:20                 ` Jason Wang
     [not found]                 ` <20220324120217.3746-1-hdanton@sina.com>
2022-03-24 12:24                   ` Eli Cohen
2022-03-25  3:22                     ` Jason Wang
2022-03-25  6:45                       ` Michael S. Tsirkin
2022-03-25  7:53                         ` Jason Wang

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=CACGkMEt-PRCsBQ+EJVGeWGikJfLk-0M1dRPMqnp9YC5R4HYAjQ@mail.gmail.com \
    --to=jasowang@redhat.com \
    --cc=elic@nvidia.com \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.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).