qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, jasowang@redhat.com, quintela@redhat.com,
	mst@redhat.com, eblake@redhat.com, armbru@redhat.com,
	germano@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 4/9] migration: Switch to using announce timer
Date: Wed, 30 Jan 2019 10:47:17 +0000	[thread overview]
Message-ID: <20190130104717.GH15904@redhat.com> (raw)
In-Reply-To: <20190130103236.18302-5-dgilbert@redhat.com>

On Wed, Jan 30, 2019 at 10:32:31AM +0000, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> 
> Switch the announcements to using the new announce timer.
> Move the code that does it to announce.c rather than savevm
> because it really has nothing to do with the actual migration.
> 
> Migration starts the announce from bh's and so they're all
> in the main thread/bql, and so there's never any racing with
> the timers themselves.
> 
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
>  include/migration/misc.h | 10 ------
>  include/net/announce.h   |  2 ++
>  include/sysemu/sysemu.h  |  2 --
>  migration/migration.c    |  2 +-
>  migration/migration.h    |  4 +++
>  migration/savevm.c       | 72 ++--------------------------------------
>  migration/trace-events   |  1 -
>  net/announce.c           | 67 +++++++++++++++++++++++++++++++++++++
>  net/trace-events         |  4 +++
>  9 files changed, 81 insertions(+), 83 deletions(-)


> +#ifndef ETH_P_RARP
> +#define ETH_P_RARP 0x8035
> +#endif
> +#define ARP_HTYPE_ETH 0x0001
> +#define ARP_PTYPE_IP 0x0800
> +#define ARP_OP_REQUEST_REV 0x3
> +
> +static int announce_self_create(uint8_t *buf,
> +                                uint8_t *mac_addr)
> +{
> +    /* Ethernet header. */
> +    memset(buf, 0xff, 6);         /* destination MAC addr */
> +    memcpy(buf + 6, mac_addr, 6); /* source MAC addr */
> +    *(uint16_t *)(buf + 12) = htons(ETH_P_RARP); /* ethertype */
> +
> +    /* RARP header. */
> +    *(uint16_t *)(buf + 14) = htons(ARP_HTYPE_ETH); /* hardware addr space */
> +    *(uint16_t *)(buf + 16) = htons(ARP_PTYPE_IP); /* protocol addr space */
> +    *(buf + 18) = 6; /* hardware addr length (ethernet) */
> +    *(buf + 19) = 4; /* protocol addr length (IPv4) */
> +    *(uint16_t *)(buf + 20) = htons(ARP_OP_REQUEST_REV); /* opcode */
> +    memcpy(buf + 22, mac_addr, 6); /* source hw addr */
> +    memset(buf + 28, 0x00, 4);     /* source protocol addr */
> +    memcpy(buf + 32, mac_addr, 6); /* target hw addr */
> +    memset(buf + 38, 0x00, 4);     /* target protocol addr */
> +
> +    /* Padding to get up to 60 bytes (ethernet min packet size, minus FCS). */
> +    memset(buf + 42, 0x00, 18);
> +
> +    return 60; /* len (FCS will be added by hardware) */
> +}

I think I would suggest defining a packed struct for the ethernet
packet we're sending, so we can just reference named fields instead
of magic offsets. Then I realized this patch is just moving some
pre-existing code, so it is probably better to leave it as it is
in this patch, as mixing code movement with refactoring is bad
practice. If anyone fancies doing a latter patch to use a struct
though, it might be nice.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  reply	other threads:[~2019-01-30 10:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30 10:32 [Qemu-devel] [PATCH v2 0/9] Network announce changes Dr. David Alan Gilbert (git)
2019-01-30 10:32 ` [Qemu-devel] [PATCH v2 1/9] net: Introduce announce timer Dr. David Alan Gilbert (git)
2019-01-30 10:32 ` [Qemu-devel] [PATCH v2 2/9] migration: Add announce parameters Dr. David Alan Gilbert (git)
2019-01-30 10:43   ` Daniel P. Berrangé
2019-01-30 10:54     ` Dr. David Alan Gilbert
2019-01-30 10:59       ` Daniel P. Berrangé
2019-01-30 12:01         ` Dr. David Alan Gilbert
2019-01-30 14:48           ` Daniel P. Berrangé
2019-01-30 10:32 ` [Qemu-devel] [PATCH v2 3/9] virtio-net: Switch to using announce timer Dr. David Alan Gilbert (git)
2019-01-30 10:32 ` [Qemu-devel] [PATCH v2 4/9] migration: " Dr. David Alan Gilbert (git)
2019-01-30 10:47   ` Daniel P. Berrangé [this message]
2019-01-30 16:41     ` Michael S. Tsirkin
2019-01-30 10:32 ` [Qemu-devel] [PATCH v2 5/9] net: Add a network device specific self-announcement ability Dr. David Alan Gilbert (git)
2019-01-30 10:32 ` [Qemu-devel] [PATCH v2 6/9] virtio-net: Allow qemu_announce_self to trigger virtio announcements Dr. David Alan Gilbert (git)
2019-01-30 10:32 ` [Qemu-devel] [PATCH v2 7/9] qmp: Add announce-self command Dr. David Alan Gilbert (git)
2019-01-30 10:32 ` [Qemu-devel] [PATCH v2 8/9] hmp: Add hmp_announce_self Dr. David Alan Gilbert (git)
2019-01-30 10:32 ` [Qemu-devel] [PATCH v2 9/9] tests: Add a test for qemu self announcements Dr. David Alan Gilbert (git)

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=20190130104717.GH15904@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=germano@redhat.com \
    --cc=jasowang@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).