From: "Zhang, Chen" <chen.zhang@intel.com>
To: Jason Wang <jasowang@redhat.com>, qemu-dev <qemu-devel@nongnu.org>
Cc: Daniel Cho <danielcho@qnap.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Zhang Chen <zhangckid@gmail.com>
Subject: RE: [PATCH 0/2] net/colo-compare.c: Expose more COLO internal
Date: Wed, 4 Mar 2020 07:59:56 +0000 [thread overview]
Message-ID: <16d27cc5e749412ebfff71cdb0de1e34@intel.com> (raw)
In-Reply-To: <20200223205805.26412-1-chen.zhang@intel.com>
Hi all,
Please give me some comments, this patch need by users(QNAP...).
Thanks
Zhang Chen
> -----Original Message-----
> From: Zhang, Chen <chen.zhang@intel.com>
> Sent: Monday, February 24, 2020 4:58 AM
> To: Jason Wang <jasowang@redhat.com>; qemu-dev <qemu-
> devel@nongnu.org>
> Cc: Zhang Chen <zhangckid@gmail.com>; Dr . David Alan Gilbert
> <dgilbert@redhat.com>; Daniel Cho <danielcho@qnap.com>; Zhang, Chen
> <chen.zhang@intel.com>
> Subject: [PATCH 0/2] net/colo-compare.c: Expose more COLO internal
>
> From: Zhang Chen <chen.zhang@intel.com>
>
> Make a way to config COLO parameter detailed according to user cases and
> environment.
>
> Zhang Chen (2):
> net/colo-compare.c: Expose "compare_timeout" to user
> net/colo-compare.c: Expose "expired_scan_cycle" to user
>
> net/colo-compare.c | 95
> +++++++++++++++++++++++++++++++++++++++++++---
> qemu-options.hx | 6 ++-
> 2 files changed, 94 insertions(+), 7 deletions(-)
>
> --
> 2.17.1
next prev parent reply other threads:[~2020-03-04 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 20:58 [PATCH 0/2] net/colo-compare.c: Expose more COLO internal Zhang Chen
2020-02-23 20:58 ` [PATCH 1/2] net/colo-compare.c: Expose "compare_timeout" to user Zhang Chen
2020-02-23 20:58 ` [PATCH 2/2] net/colo-compare.c: Expose "expired_scan_cycle" " Zhang Chen
2020-03-04 7:59 ` Zhang, Chen [this message]
2020-03-17 8:25 ` [PATCH 0/2] net/colo-compare.c: Expose more COLO internal Zhang, Chen
2020-03-18 2:47 ` Jason Wang
2020-03-18 7:00 ` Zhang, Chen
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=16d27cc5e749412ebfff71cdb0de1e34@intel.com \
--to=chen.zhang@intel.com \
--cc=danielcho@qnap.com \
--cc=dgilbert@redhat.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhangckid@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 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).