All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Christian Brunner <chb@muc.de>
Cc: Yehuda Sadeh Weinraub <yehudasa@gmail.com>, ceph-devel@vger.kernel.org
Subject: Re: [PATCH] qemu-kvm/rbd: add queueing delay based on queuesize (using use qemu_mutex_* and qemu_cond_*)
Date: Fri, 23 Jul 2010 10:56:17 +0200	[thread overview]
Message-ID: <4C495931.2090705@redhat.com> (raw)
In-Reply-To: <AANLkTikUykm7LOtlu1BWQwWr28w548tLI-gylJcJs8Mq@mail.gmail.com>

Am 21.07.2010 21:18, schrieb Christian Brunner:
> 2010/7/20 Yehuda Sadeh Weinraub <yehudasa@gmail.com>:
>>> +        while  (s->queuesize > MAX_QUEUE_SIZE) {
>>> +            qemu_mutex_lock(s->queue_mutex);
>>> +            qemu_cond_wait(s->queue_threshold, s->queue_mutex);
>>> +            qemu_mutex_unlock(s->queue_mutex);
>>> +        }
>>
>> Actually we shouldn't be waiting inside the aio handler. We should
>> probably be feeding the request into some wait queue and have a
>> separate thread that drains all those requests out. Though this
>> wouldn't help us in throttling the client memory, it's probably a more
>> correct way to handle the problem.
> 
> I agree with you, however I don't think that this is worth the effort.
> I've never seen this occur when running a virtual machine, only when
> running qemu-io.
> 
> @Kevin: Did you follow this thread? What is your opinion?

No, I'm not subscribed to your mailing list and qemu-devel isn't CCed.

I'm not entirely sure what kind of queue this is about, but are you sure
that it can only happen with large requests as issued by qemu-io? Can
many small requests cause the same, especially with a slow network
connection (or it might even go down for some reason?

If I understand correctly, waiting here could cause qemu to become
unresponsive, right?

Kevin

  reply	other threads:[~2010-07-23  8:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-14 13:35 [PATCH] qemu-kvm/rbd: add queueing delay based on queuesize (using use qemu_mutex_* and qemu_cond_*) Christian Brunner
2010-07-20 20:42 ` Yehuda Sadeh Weinraub
2010-07-21 19:18   ` Christian Brunner
2010-07-23  8:56     ` Kevin Wolf [this message]
2010-07-23 16:46       ` Sage Weil
2010-07-23 18:51         ` Christian Brunner

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=4C495931.2090705@redhat.com \
    --to=kwolf@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=chb@muc.de \
    --cc=yehudasa@gmail.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.