From: Yehuda Sadeh Weinraub <yehudasa@gmail.com>
To: Christian Brunner <chb@muc.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
Simone Gotti <simone.gotti@gmail.com>,
ceph-devel@vger.kernel.org, qemu-devel@nongnu.org,
kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: [PATCH] ceph/rbd block driver for qemu-kvm (v3)
Date: Tue, 13 Jul 2010 12:41:17 -0700 [thread overview]
Message-ID: <AANLkTikWM-990doMte8tKOxZ63vbzQVHpMefZmdD8B2_@mail.gmail.com> (raw)
In-Reply-To: <20100713192338.GA25126@sir.home>
On Tue, Jul 13, 2010 at 12:23 PM, Christian Brunner <chb@muc.de> wrote:
> On Tue, Jul 13, 2010 at 11:27:03AM -0700, Yehuda Sadeh Weinraub wrote:
>> >
>> > There is another problem with very large i/o requests. I suspect that
>> > this can be triggered only
>> > with qemu-io and not in kvm, but I'll try to get a proper solution it anyway.
>> >
>>
>> Have you made any progress with this issue? Just note that there were
>> a few changes we introduced recently (a format change that allows
>> renaming of rbd images, and some snapshots support), so everything
>> will needed to be reposted once we figure out the aio issue.
>
> Attached is a patch where I'm trying to solve the issue
> with pthreads locking. It works well with qemu-io, but I'm
> not sure if there are interferences with other threads in
> qemu/kvm (I didn't have time to test this, yet).
>
> Another thing I'm not sure about is the fact, that these
> large I/O requests only happen with qemu-io. I've never seen
> this happen inside a virtual machine. So do we really have
> to fix this, as it is only a warning message (laggy).
>
We can have it configurable, and by default not use it. We don't need
to feed the osds with more data that they can digest anyway, since
that will only increase our memory usage -- whether it's just a
warning or a real error. So a bounded approach that doesn't hurt
performance makes sense.
I'll merge this one into our tree so that it could get some broader
testing, however, I think the qemu code requires using the qemu_cond
wrappers instead of directly using the pthread_cond_*().
Thanks,
Yehuda
WARNING: multiple messages have this Message-ID (diff)
From: Yehuda Sadeh Weinraub <yehudasa@gmail.com>
To: Christian Brunner <chb@muc.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
ceph-devel@vger.kernel.org, Simone Gotti <simone.gotti@gmail.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: [PATCH] ceph/rbd block driver for qemu-kvm (v3)
Date: Tue, 13 Jul 2010 12:41:17 -0700 [thread overview]
Message-ID: <AANLkTikWM-990doMte8tKOxZ63vbzQVHpMefZmdD8B2_@mail.gmail.com> (raw)
In-Reply-To: <20100713192338.GA25126@sir.home>
On Tue, Jul 13, 2010 at 12:23 PM, Christian Brunner <chb@muc.de> wrote:
> On Tue, Jul 13, 2010 at 11:27:03AM -0700, Yehuda Sadeh Weinraub wrote:
>> >
>> > There is another problem with very large i/o requests. I suspect that
>> > this can be triggered only
>> > with qemu-io and not in kvm, but I'll try to get a proper solution it anyway.
>> >
>>
>> Have you made any progress with this issue? Just note that there were
>> a few changes we introduced recently (a format change that allows
>> renaming of rbd images, and some snapshots support), so everything
>> will needed to be reposted once we figure out the aio issue.
>
> Attached is a patch where I'm trying to solve the issue
> with pthreads locking. It works well with qemu-io, but I'm
> not sure if there are interferences with other threads in
> qemu/kvm (I didn't have time to test this, yet).
>
> Another thing I'm not sure about is the fact, that these
> large I/O requests only happen with qemu-io. I've never seen
> this happen inside a virtual machine. So do we really have
> to fix this, as it is only a warning message (laggy).
>
We can have it configurable, and by default not use it. We don't need
to feed the osds with more data that they can digest anyway, since
that will only increase our memory usage -- whether it's just a
warning or a real error. So a bounded approach that doesn't hurt
performance makes sense.
I'll merge this one into our tree so that it could get some broader
testing, however, I think the qemu code requires using the qemu_cond
wrappers instead of directly using the pthread_cond_*().
Thanks,
Yehuda
next prev parent reply other threads:[~2010-07-13 19:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 19:31 [PATCH] ceph/rbd block driver for qemu-kvm (v3) Christian Brunner
2010-05-31 19:31 ` [Qemu-devel] " Christian Brunner
2010-06-01 8:43 ` Kevin Wolf
2010-06-02 7:42 ` Christian Brunner
2010-06-11 19:51 ` Simone Gotti
2010-06-11 19:51 ` [Qemu-devel] " Simone Gotti
2010-06-17 19:05 ` Christian Brunner
2010-06-17 19:05 ` [Qemu-devel] " Christian Brunner
2010-06-18 10:09 ` Kevin Wolf
2010-06-18 10:09 ` Kevin Wolf
2010-06-19 15:48 ` Christian Brunner
2010-06-19 15:48 ` Christian Brunner
2010-07-13 18:27 ` Yehuda Sadeh Weinraub
2010-07-13 18:27 ` Yehuda Sadeh Weinraub
2010-07-13 19:23 ` Christian Brunner
2010-07-13 19:23 ` Christian Brunner
2010-07-13 19:23 ` Christian Brunner
2010-07-13 19:41 ` Yehuda Sadeh Weinraub [this message]
2010-07-13 19:41 ` Yehuda Sadeh Weinraub
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=AANLkTikWM-990doMte8tKOxZ63vbzQVHpMefZmdD8B2_@mail.gmail.com \
--to=yehudasa@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=chb@muc.de \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=simone.gotti@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.