From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/2] Allow ipv6 for migration
Date: Wed, 16 Mar 2011 22:01:04 +0100 [thread overview]
Message-ID: <cover.1300297944.git.quintela@redhat.com> (raw)
Hi
1st patch moves migration to use getaddrinfo() instead of parse_host_port().
This allows us to use ipv6 addresses. As an extra bonus, now we can use
names from /etc/services.
Code for net_socket_listen_init() and net_socket_connect_init() was
almost identical to migration one, so also changed that ones.
The difference were small based on how error codes were handled.
After discussing with Anthony, it appears that the right ones are
the migration ones.
Tested (the migration code) with:
- "tcp:foo:4444" ipv4 name
- "tcp:foo6:4444" ipv6 name
- "tcp:0:4444"
- "tcp:foo6:iqobject" (this was an unused entry on my machine /etc/services)
iqobject 48619/tcp # iqobject
- "tcp::4444": let the kernel make a choice
Please review.
Later, Juan.
Juan Quintela (2):
Use getaddrinfo for migration
net/socket: allow ipv6 for net_socket_listen_init and
net_socket_connect_init
migration-tcp.c | 53 ++++++-------------------
net.c | 113 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
net/socket.c | 60 +++++------------------------
qemu_socket.h | 3 +
4 files changed, 140 insertions(+), 89 deletions(-)
--
1.7.4
next reply other threads:[~2011-03-16 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 21:01 Juan Quintela [this message]
2011-03-16 21:01 ` [Qemu-devel] [PATCH 1/2] Use getaddrinfo for migration Juan Quintela
2011-03-16 22:06 ` Peter Maydell
2011-03-16 22:20 ` [Qemu-devel] " Juan Quintela
2011-03-16 21:01 ` [Qemu-devel] [PATCH 2/2] net/socket: allow ipv6 for net_socket_listen_init and net_socket_connect_init Juan Quintela
2011-03-16 21:30 ` Peter Maydell
2011-03-16 22:22 ` [Qemu-devel] " Juan Quintela
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=cover.1300297944.git.quintela@redhat.com \
--to=quintela@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).