From: Josh Durgin <josh.durgin@inktank.com>
To: =?gb18030?Q?=D2=B6=C9=DC=E8=A1?= <yeshaochen@foxmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] =?gb18030?b?u9i4tKO6ILvYuLSjuiC72Li0o7ogu9i4tKO6ILvYuLSjuiC72Li0o7ogIHFlbXUgdm0gYmlnIG5ldHdvcmsgbGF0ZW5jeSB3aGVu?= =?gb18030?q?_met_heavy_io?=
Date: Thu, 16 Jan 2014 22:57:29 -0800 [thread overview]
Message-ID: <52D8D459.2050205@inktank.com> (raw)
In-Reply-To: <tencent_0C119822426FB8B81E60F6EB@qq.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030; format=flowed, Size: 1267 bytes --]
On 01/15/2014 10:12 PM, Ò¶ÉÜè¡ wrote:
> Hi Josh
>
> # strings /usr/bin/qemu-system-x86_64 | grep rbd_aio
> rbd_aio_write
> rbd_aio_flush
> rbd_aio_read
> rbd_aio_create_completion
> rbd_aio_release
> rbd_aio_discard
> rbd_aio_get_return_value
>
> So, librbd's asynchronous flush is being used.
>
> I set log settings, fetch the log and ping log with timestamped, all
> logs are in the attachment.
Excellent, thanks.
> It seems that I doesn't have permission to generate a new issue
> on tracker.ceph.com, when I click the 'Register' it show a 'internal
> error' page.
Seems to be working for me. In any case, I created
http://tracker.ceph.com/issues/7165 to track the problem.
Looking through the logs, it may have been already solved in
a couple commits after 0.67.5. Namely, the cache was starting the flush
of too much dirty data at once while holding a lock, preventing other
I/O from the guest from starting, and thus blocking the qemu thread
handling the I/O.
I added the relevant commits to the wip-objectcacher-flusher-dumpling
branch in ceph.git. Could you install librbd from that branch and see
if it fixes the problem? Instructions for getting these packages are:
http://ceph.com/docs/master/install/get-packages/#add-ceph-development
Thanks,
Josh
prev parent reply other threads:[~2014-01-17 6:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 6:55 [Qemu-devel] qemu vm big network latency when met heavy io =?gb18030?B?0rbJ3Oih?=
2014-01-08 4:44 ` Stefan Hajnoczi
[not found] ` <CANzgAZnvTmKc1NKoJPRLTT-L-ppYWoUko6JKHfpMzOGboLh8YA@mail.gmail.com>
2014-01-09 2:47 ` [Qemu-devel] [Qemu-discuss] " Stefan Hajnoczi
[not found] ` <tencent_1499A979046903942D656C7F@qq.com>
[not found] ` <CAJSP0QV0G=reFHP4N=njGUcZxP-x-Ef=L0U3zj5DHfRGjrgvrw@mail.gmail.com>
[not found] ` <tencent_2A1DD90F3E8281BD36D67A63@qq.com>
[not found] ` <CAJSP0QW1m7UL27_CROjXsG2sBse+Md9fSWMgXzTZWVaxvhaz7Q@mail.gmail.com>
[not found] ` <tencent_74BAFF5462FB3EA25C557F97@qq.com>
[not found] ` <CAJSP0QXgjkHf3mFzSOm5rLjd5+uHpHDPTcKPFruZ0naTiN5yHg@mail.gmail.com>
2014-01-14 6:24 ` [Qemu-devel] 回复: 回复: 回复: " Josh Durgin
[not found] ` <tencent_35E422F81535374D5992C5AB@qq.com>
2014-01-14 7:58 ` [Qemu-devel] =?gb18030?b?u9i4tKO6ILvYuLSjuiC72Li0o7ogu9i4tKO6ICBx?= =?gb18030?q?emu_vm_big_network_latency_when_met_heavy_io?= Josh Durgin
[not found] ` <tencent_043538FC1C65245E76ED4CB0@qq.com>
2014-01-16 2:25 ` [Qemu-devel] =?gb18030?b?u9i4tKO6ILvYuLSjuiC72Li0o7ogu9i4tKO6ILvY?= =?gb18030?q?=B8=B4=A3=BA__qemu_vm_big_network_latency_when_met_heavy_io?= Josh Durgin
[not found] ` <tencent_0C119822426FB8B81E60F6EB@qq.com>
2014-01-17 6:57 ` Josh Durgin [this message]
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=52D8D459.2050205@inktank.com \
--to=josh.durgin@inktank.com \
--cc=qemu-devel@nongnu.org \
--cc=yeshaochen@foxmail.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.