qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Roman Penyaev <roman.penyaev@profitbricks.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 3/3] linux-aio: process completions from ioq_submit()
Date: Tue, 19 Jul 2016 13:47:00 +0200	[thread overview]
Message-ID: <fd2a80fb-272f-8341-f0ca-0b195771fdbd@redhat.com> (raw)
In-Reply-To: <CAJrWOzAu6Cyx6OPL9SEeTcrB+ZdSyHAq0dLqZa-51VfB4jpcAg@mail.gmail.com>



On 19/07/2016 13:44, Roman Penyaev wrote:
>>> >>
>>> >> Can this leave I/O stuck if in_queue > 0 && in_flight == 0 after the
>>> >> return from qemu_laio_process_completions?  I think you need to goto the
>>> >> beginning of the function to submit more I/O requests in that case.
> Not quite.  I still leave '&s->e' as set, so we will return in a generic
> qemu_laio_completion_cb(), will do 'event_notifier_test_and_clear(&s->e)'
> and again will process events with normal submission.
> 
> IMHO this is better variant than spinning inside ioq_submit doing goto.
> We do not occupy the whole events processing for our IO needs and give
> a chance to complete other stuff.  But of course this is guts feeling
> and I do not have any serious numbers.

That's fine as long as it doesn't hang. :)

Paolo

  reply	other threads:[~2016-07-19 11:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19 10:25 [Qemu-devel] [PATCH 0/3] linux-aio: reduce completion latency Roman Pen
2016-07-19 10:25 ` [Qemu-devel] [PATCH 1/3] linux-aio: consume events in userspace instead of calling io_getevents Roman Pen
2016-07-19 10:25 ` [Qemu-devel] [PATCH 2/3] linux-aio: split processing events function Roman Pen
2016-07-19 10:25 ` [Qemu-devel] [PATCH 3/3] linux-aio: process completions from ioq_submit() Roman Pen
2016-07-19 10:36   ` Paolo Bonzini
2016-07-19 11:18     ` Roman Penyaev
2016-07-19 11:30       ` Paolo Bonzini
2016-07-19 11:44       ` Roman Penyaev
2016-07-19 11:47         ` Paolo Bonzini [this message]
2016-07-19 11:52           ` Roman Penyaev

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=fd2a80fb-272f-8341-f0ca-0b195771fdbd@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=roman.penyaev@profitbricks.com \
    --cc=stefanha@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).