From: Yong Huang <yong.huang@smartx.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: Peter Xu <peterx@redhat.com>,
qemu-devel@nongnu.org,
Hailiang Zhang <zhanghailiang@xfusion.com>
Subject: Re: [PATCH] migration: Put thread names together with macros
Date: Sat, 12 Oct 2024 15:39:25 +0800 [thread overview]
Message-ID: <CAK9dgmZ89J1N6iY+1xRYJwb8K8FVWqx7MbtLFMFvasDVTDDdqg@mail.gmail.com> (raw)
In-Reply-To: <87v7xyr1jz.fsf@suse.de>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
On Sat, Oct 12, 2024 at 1:29 AM Fabiano Rosas <farosas@suse.de> wrote:
> Peter Xu <peterx@redhat.com> writes:
>
> > Keep migration thread names together, so it's easier to see a list of all
> > possible migration threads.
> >
> > Still two functional changes below besides the macro defintions:
> >
> > - There's one dirty rate thread that we overlooked before, now we add
> > that too and name it as "mig/dirtyrate" following the old rules.
> >
> > - The old name "mig/src/rp-thr" has "-thr" but it may not be useful if
> > it's a thread name anyway, while "rp" can be slightly hard to read.
> > Taking this chance to rename it to "mig/src/return", hopefully a better
> > name.
> >
> > Signed-off-by: Peter Xu <peterx@redhat.com>
>
> Reviewed-by: Fabiano Rosas <farosas@suse.de>
>
Acked-by: Hyman Huang <yong.huang@smartx.com>
--
Best regards
[-- Attachment #2: Type: text/html, Size: 2011 bytes --]
next prev parent reply other threads:[~2024-10-12 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 15:36 [PATCH] migration: Put thread names together with macros Peter Xu
2024-10-11 17:29 ` Fabiano Rosas
2024-10-12 7:39 ` Yong Huang [this message]
2024-10-14 6:05 ` Zhang, Chen
2024-10-15 13:58 ` Peter Xu
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=CAK9dgmZ89J1N6iY+1xRYJwb8K8FVWqx7MbtLFMFvasDVTDDdqg@mail.gmail.com \
--to=yong.huang@smartx.com \
--cc=farosas@suse.de \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhanghailiang@xfusion.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).