From: Vlad Yasevich <vyasevic@redhat.com>
To: quintela@redhat.com
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com, germano@redhat.com,
lvivier@redhat.com, jasowang@redhat.com, jdenemar@redhat.com,
kashyap@redhat.com, armbru@redhat.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH 01/12] migration: Introduce announce parameters
Date: Tue, 30 May 2017 09:45:28 -0400 [thread overview]
Message-ID: <9c89a465-1268-4213-2ae3-dd8f034b48a7@redhat.com> (raw)
In-Reply-To: <87poeqhdji.fsf@secure.mitica>
On 05/30/2017 05:58 AM, Juan Quintela wrote:
> Vladislav Yasevich <vyasevic@redhat.com> wrote:
>> Add parameters that control RARP/GARP announcement timeouts.
>> The parameters structure is added to the QAPI and a qmp command
>> is added to set/get the parameter data.
>>
>> Based on work by "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>>
>> Signed-off-by: Vladislav Yasevich <vyasevic@redhat.com>
>
> Hi
>
>> diff --git a/migration/savevm.c b/migration/savevm.c
>> index f5e8194..cee2837 100644
>> --- a/migration/savevm.c
>> +++ b/migration/savevm.c
>> @@ -78,6 +78,104 @@ static struct mig_cmd_args {
>> [MIG_CMD_MAX] = { .len = -1, .name = "MAX" },
>> };
>>
>
> Once that you are touching this, shouldn't it be better to be in
> net/<somewhere>?
> They have nothing to do with migration really.
>
Yeah, I considered this, but could really find a good slot for them.
I can either put them into net.c directly or pull them out into their
own little file.
>
>> +#define QEMU_ANNOUNCE_INITIAL 50
>> +#define QEMU_ANNOUNCE_MAX 550
>> +#define QEMU_ANNOUNCE_ROUNDS 5
>> +#define QEMU_ANNOUNCE_STEP 100
>> +
>> +AnnounceParameters *qemu_get_announce_params(void)
>> +{
>> + static AnnounceParameters announce = {
>> + .initial = QEMU_ANNOUNCE_INITIAL,
>> + .max = QEMU_ANNOUNCE_MAX,
>> + .rounds = QEMU_ANNOUNCE_ROUNDS,
>> + .step = QEMU_ANNOUNCE_STEP,
>> + };
>> +
>> + return &announce;
>> +}
>> +
>> +void qemu_fill_announce_parameters(AnnounceParameters **to,
>> + AnnounceParameters *from)
>> +{
>> + AnnounceParameters *params;
>> +
>> + params = *to = g_malloc0(sizeof(*params));
>> + params->has_initial = true;
>> + params->initial = from->initial;
>> + params->has_max = true;
>> + params->max = from->max;
>> + params->has_rounds = true;
>> + params->rounds = from->rounds;
>> + params->has_step = true;
>> + params->step = from->step;
>> +}
>> +
>> +bool qemu_validate_announce_parameters(AnnounceParameters *params, Error **errp)
>> +{
>> + if (params->has_initial &&
>> + (params->initial < 1 || params->initial > 100000)) {
>
> This is independent of this patch, but we really need a macro:
> CHECK(field, mininum, maximum)
>
> We repeat this left and right.
>
>> +void qemu_set_announce_parameters(AnnounceParameters *announce_params,
>> + AnnounceParameters *params)
>
>> +void qmp_announce_set_parameters(AnnounceParameters *params, Error **errp)
>
> Really similar functions name. I assume by know that the 1st function
> is used somewhere else in the series.
>
Yes, the first function is going to be used later.
Thanks
-vlad
next prev parent reply other threads:[~2017-05-30 13:45 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 18:05 [Qemu-devel] [PATCH 00/12] self-announce updates Vladislav Yasevich
2017-05-24 18:05 ` [Qemu-devel] [PATCH 01/12] migration: Introduce announce parameters Vladislav Yasevich
2017-05-26 4:03 ` Jason Wang
2017-05-26 13:06 ` Vlad Yasevich
2017-05-30 18:57 ` Dr. David Alan Gilbert
2017-06-01 7:02 ` Jason Wang
2017-06-01 13:45 ` Vlad Yasevich
2017-06-01 14:02 ` Dr. David Alan Gilbert
2017-05-26 13:08 ` Eric Blake
2017-05-26 13:17 ` Vlad Yasevich
2017-05-30 9:58 ` Juan Quintela
2017-05-30 13:45 ` Vlad Yasevich [this message]
2017-05-30 19:08 ` Dr. David Alan Gilbert
2017-05-24 18:05 ` [Qemu-devel] [PATCH 02/12] migration: Introduce announcement timer Vladislav Yasevich
2017-05-26 4:13 ` Jason Wang
2017-05-30 10:00 ` Juan Quintela
2017-05-24 18:05 ` [Qemu-devel] [PATCH 03/12] migration: Switch to using " Vladislav Yasevich
2017-05-26 4:16 ` Jason Wang
2017-05-26 13:01 ` Vlad Yasevich
2017-05-30 10:10 ` Juan Quintela
2017-05-30 13:46 ` Vlad Yasevich
2017-05-30 19:19 ` Dr. David Alan Gilbert
2017-05-30 19:34 ` Vlad Yasevich
2017-05-24 18:05 ` [Qemu-devel] [PATCH 04/12] net: Add a network device specific self-announcement ability Vladislav Yasevich
2017-05-26 4:17 ` Jason Wang
2017-05-24 18:05 ` [Qemu-devel] [PATCH 05/12] virtio-net: Allow qemu_announce_self to trigger virtio announcements Vladislav Yasevich
2017-05-26 4:21 ` Jason Wang
2017-05-24 18:05 ` [Qemu-devel] [PATCH 06/12] qmp: Expose qemu_announce_self as a qmp command Vladislav Yasevich
2017-05-26 13:16 ` Eric Blake
2017-05-26 13:19 ` Vlad Yasevich
2017-05-30 10:11 ` Juan Quintela
2017-05-30 13:49 ` Vlad Yasevich
2017-05-30 14:24 ` Juan Quintela
2017-05-30 14:43 ` Vlad Yasevich
2017-05-30 14:14 ` Daniel P. Berrange
2017-05-30 15:01 ` Vlad Yasevich
2017-05-24 18:05 ` [Qemu-devel] [PATCH 07/12] migration: Allow for a limited number of announce timers Vladislav Yasevich
2017-05-30 10:13 ` Juan Quintela
2017-05-30 19:31 ` Dr. David Alan Gilbert
2017-05-24 18:05 ` [Qemu-devel] [PATCH 08/12] announce_timer: Add ability to reset an existing Vladislav Yasevich
2017-05-30 10:15 ` Juan Quintela
2017-05-30 19:35 ` Dr. David Alan Gilbert
2017-05-30 20:01 ` Vlad Yasevich
2017-05-24 18:05 ` [Qemu-devel] [PATCH 09/12] hmp: add announce paraters info/set Vladislav Yasevich
2017-05-30 10:18 ` Juan Quintela
2017-05-30 13:57 ` Vlad Yasevich
2017-05-24 18:05 ` [Qemu-devel] [PATCH 10/12] hmp: Add hmp_announce_self Vladislav Yasevich
2017-05-31 9:47 ` Dr. David Alan Gilbert
2017-05-24 18:05 ` [Qemu-devel] [PATCH 11/12] tests/test-hmp: Add announce parameter tests Vladislav Yasevich
2017-05-31 9:53 ` Dr. David Alan Gilbert
2017-05-24 18:05 ` [Qemu-devel] [PATCH 12/12] tests: Add a test for qemu self announcments Vladislav Yasevich
2017-05-24 18:19 ` [Qemu-devel] [PATCH 00/12] self-announce updates no-reply
2017-05-24 18:38 ` no-reply
2017-05-24 18:40 ` no-reply
2017-05-31 10:29 ` Dr. David Alan Gilbert
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=9c89a465-1268-4213-2ae3-dd8f034b48a7@redhat.com \
--to=vyasevic@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=germano@redhat.com \
--cc=jasowang@redhat.com \
--cc=jdenemar@redhat.com \
--cc=kashyap@redhat.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).