qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Xiao Guangrong <guangrong.xiao@gmail.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: mst@redhat.com, mtosatti@redhat.com, qemu-devel@nongnu.org,
	kvm@vger.kernel.org, peterx@redhat.com, wei.w.wang@intel.com,
	jiang.biao2@zte.com.cn, eblake@redhat.com, quintela@redhat.com,
	cota@braap.org, Xiao Guangrong <xiaoguangrong@tencent.com>
Subject: Re: [Qemu-devel] [PATCH v3 3/5] migration: use threaded workqueue for compression
Date: Mon, 26 Nov 2018 16:00:34 +0800	[thread overview]
Message-ID: <c36abd0a-fcca-c9c2-11a7-c5d39a386418@gmail.com> (raw)
In-Reply-To: <20181123182918.GI2373@work-vm>



On 11/24/18 2:29 AM, Dr. David Alan Gilbert wrote:

>>>>   static void
>>>> -update_compress_thread_counts(const CompressParam *param, int bytes_xmit)
>>>> +update_compress_thread_counts(CompressData *cd, int bytes_xmit)
>>>
>>> Keep the const?

Yes, indeed. Will correct it in the next version.

>>>> +    if (deflateInit(&cd->stream, migrate_compress_level()) != Z_OK) {
>>>> +        g_free(cd->originbuf);
>>>> +        return -1;
>>>> +    }
>>>
>>> Please print errors if you fail in any case so we can easily tell what
>>> happened.

Sure, will do.

>>>> +        if (wait) {
>>>> +            cpu_relax();
>>>> +            goto retry;
>>>
>>> Is there nothing better we can use to wait without eating CPU time?
>>
>> There is a mechanism to wait without eating CPU time in the data
>> structure, but it makes sense to busy wait.  There are 4 threads in the
>> workqueue, so you have to compare 1/4th of the time spent compressing a
>> page, with the trip into the kernel to wake you up.  You're adding 20%
>> CPU usage, but I'm not surprised it's worthwhile.
> 
> Hmm OK; in that case it does at least need a comment because it's a bit
> odd, and we should watch out how that scales - I guess it's less of
> an overhead the more threads you use.
> 

Sure, will add some comments to explain the purpose.

  reply	other threads:[~2018-11-26  8:00 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-22  7:20 [Qemu-devel] [PATCH v3 0/5] migration: improve multithreads guangrong.xiao
2018-11-22  7:20 ` [Qemu-devel] [PATCH v3 1/5] bitops: introduce change_bit_atomic guangrong.xiao
2018-11-23 10:23   ` Dr. David Alan Gilbert
2018-11-28  9:35   ` Juan Quintela
2018-11-22  7:20 ` [Qemu-devel] [PATCH v3 2/5] util: introduce threaded workqueue guangrong.xiao
2018-11-23 11:02   ` Dr. David Alan Gilbert
2018-11-26  7:57     ` Xiao Guangrong
2018-11-26 10:56       ` Dr. David Alan Gilbert
2018-11-27  7:17         ` Xiao Guangrong
2018-11-26 18:55       ` Emilio G. Cota
2018-11-27  8:30         ` Xiao Guangrong
2018-11-24  0:12   ` Emilio G. Cota
2018-11-26  8:06     ` Xiao Guangrong
2018-11-26 18:49       ` Emilio G. Cota
2018-11-27  8:29         ` Xiao Guangrong
2018-11-24  0:17   ` Emilio G. Cota
2018-11-26  8:18     ` Xiao Guangrong
2018-11-26 10:28       ` Paolo Bonzini
2018-11-27  8:31         ` Xiao Guangrong
2018-11-27 12:49   ` Christophe de Dinechin
2018-11-27 13:51     ` Paolo Bonzini
2018-12-04 15:49       ` Christophe de Dinechin
2018-12-04 17:16         ` Paolo Bonzini
2018-12-10  3:23           ` Xiao Guangrong
2018-11-27 17:39     ` Emilio G. Cota
2018-11-28  8:55     ` Xiao Guangrong
2018-11-22  7:20 ` [Qemu-devel] [PATCH v3 3/5] migration: use threaded workqueue for compression guangrong.xiao
2018-11-23 18:17   ` Dr. David Alan Gilbert
2018-11-23 18:22     ` Paolo Bonzini
2018-11-23 18:29       ` Dr. David Alan Gilbert
2018-11-26  8:00         ` Xiao Guangrong [this message]
2018-11-22  7:20 ` [Qemu-devel] [PATCH v3 4/5] migration: use threaded workqueue for decompression guangrong.xiao
2018-11-22  7:20 ` [Qemu-devel] [PATCH v3 5/5] tests: add threaded-workqueue-bench guangrong.xiao
2018-11-22 21:25 ` [Qemu-devel] [PATCH v3 0/5] migration: improve multithreads no-reply
2018-11-22 21:35 ` no-reply

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=c36abd0a-fcca-c9c2-11a7-c5d39a386418@gmail.com \
    --to=guangrong.xiao@gmail.com \
    --cc=cota@braap.org \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jiang.biao2@zte.com.cn \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=wei.w.wang@intel.com \
    --cc=xiaoguangrong@tencent.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).