From: Gerd Hoffmann <kraxel@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/4] sockets: helper functions for qemu.
Date: Tue, 28 Oct 2008 16:10:54 +0100 [thread overview]
Message-ID: <49072B7E.9060501@redhat.com> (raw)
In-Reply-To: <20081028143119.GX18016@redhat.com>
Daniel P. Berrange wrote:
> On Tue, Oct 28, 2008 at 03:22:35PM +0100, Gerd Hoffmann wrote:
>> Daniel P. Berrange wrote:
>> Sure? I've googled a bit on this issue, looked what apache does here.
>> I've figured this can be changed per socket, with a system-wide default
>> configurable via sysctl (and different OSes have different default
>> configs here).
>
> Ah, I was mis-understanding what IPV6_V6ONLY was doing here. If that's
> portable to BSD like OS too, then I reckon that's sufficient and would
> avoid need for separate sockets.
I hope so, but didn't actually test that on something BSDish. Maybe the
BSD folks on the list can comment/test?
> Uli was demonstrating how to achieve total protocol independance
> in your code. So if someone invents something better even than
> IPv6 your code would still work. If you're happy to limit yourself
> to just IPv4 & IPv6, then the IPV6_V6ONLY trick would work.
Right now there isn't anything else, and I'd prefer to tackle the issue
of other protocols once we have them. There are also some more ipv4/v6
assumptions in the code, so other protocols wouldn't work out-of-the-box
anyway.
cheers,
Gerd
next prev parent reply other threads:[~2008-10-28 15:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 12:55 [Qemu-devel] [PATCH 0/4] ipv6 and autoport patches Gerd Hoffmann
2008-10-28 12:55 ` [Qemu-devel] [PATCH 1/4] Implement "info chardev" command Gerd Hoffmann
2008-10-28 17:08 ` Blue Swirl
2008-10-28 19:58 ` Gerd Hoffmann
2008-10-29 11:02 ` Gerd Hoffmann
2008-10-29 18:30 ` Blue Swirl
2008-10-28 20:19 ` Daniel P. Berrange
2008-10-28 21:28 ` Gerd Hoffmann
2008-10-28 12:55 ` [Qemu-devel] [PATCH 2/4] sockets: helper functions for qemu Gerd Hoffmann
2008-10-28 13:15 ` Daniel P. Berrange
2008-10-28 14:22 ` Gerd Hoffmann
2008-10-28 14:31 ` Daniel P. Berrange
2008-10-28 15:10 ` Gerd Hoffmann [this message]
2008-10-28 12:55 ` [Qemu-devel] [PATCH 3/4] sockets: switch vnc to new code, support vnc port auto-allocation Gerd Hoffmann
2008-10-28 17:25 ` Blue Swirl
2008-10-28 19:57 ` Gerd Hoffmann
2008-10-29 10:46 ` Gerd Hoffmann
2008-10-28 12:55 ` [Qemu-devel] [PATCH 4/4] sockets: switch over tcp/telnet/unix serial line to new helper functions Gerd Hoffmann
2008-10-28 15:53 ` [Qemu-devel] [PATCH 0/4] ipv6 and autoport patches Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2008-10-31 12:47 [Qemu-devel] [PATCH v2 " Gerd Hoffmann
2008-10-31 12:47 ` [Qemu-devel] [PATCH 2/4] sockets: helper functions for qemu Gerd Hoffmann
2008-10-31 17:37 ` Anthony Liguori
2008-10-31 17:50 ` Daniel P. Berrange
2008-10-31 17:58 ` Anthony Liguori
2008-10-31 19:44 ` Jamie Lokier
2008-11-03 15:35 ` Gerd Hoffmann
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=49072B7E.9060501@redhat.com \
--to=kraxel@redhat.com \
--cc=berrange@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.