All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Asias He <asias@redhat.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [PATCH 2/2] vhost: Avoid that vhost_work_flush() returns early
Date: Wed, 14 Aug 2013 17:19:06 +0200	[thread overview]
Message-ID: <520B9FEA.7090005@acm.org> (raw)
In-Reply-To: <20130814114640.GG5430@redhat.com>

On 08/14/13 13:46, Michael S. Tsirkin wrote:
> I'm confused by this explanation.
> done_seq is set here:
>                  if (work) {
>                          work->done_seq = seq;
>                          if (work->flushing)
>                                  wake_up_all(&work->done);
>                  }
>
> and work is set here:
>
>                  if (!list_empty(&dev->work_list)) {
>                          work = list_first_entry(&dev->work_list,
>                                                  struct vhost_work, node);
>                          list_del_init(&work->node);
>                          seq = work->queue_seq;
>                  }
>
> this work is processed on the next line:
>
>                  if (work) {
>                          __set_current_state(TASK_RUNNING);
>                          work->fn(work);
>                          if (need_resched())
>                                  schedule();
>                  }
>
> so how do we end up with a sequence of a work item
> that isn't processed?

I was wondering what would happen if a work item got requeued before 
done_seq is set. I think you are right and this should work fine.

Bart.

  reply	other threads:[~2013-08-14 15:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14  7:01 [PATCH 0/2] vhost_worker fixes Bart Van Assche
2013-08-14  7:02 ` [PATCH 1/2] vhost: Reduce vhost_work_flush() wakeup latency Bart Van Assche
2013-08-14 11:37   ` Michael S. Tsirkin
2013-08-14 15:22     ` Bart Van Assche
2013-08-14 17:58       ` Michael S. Tsirkin
2013-08-15  1:30         ` Asias He
2013-08-15  6:13           ` Bart Van Assche
2013-08-15  7:35             ` Michael S. Tsirkin
2013-08-14  7:03 ` [PATCH 2/2] vhost: Avoid that vhost_work_flush() returns early Bart Van Assche
2013-08-14 11:46   ` Michael S. Tsirkin
2013-08-14 15:19     ` Bart Van Assche [this message]
2013-08-14 11:39 ` [PATCH 0/2] vhost_worker fixes Michael S. Tsirkin

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=520B9FEA.7090005@acm.org \
    --to=bvanassche@acm.org \
    --cc=asias@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.