From: Jan Kiszka <jan.kiszka@web.de>
To: Alex Bradbury <asb@asbradbury.org>
Cc: Zhi Yong Wu <zwu.kernel@gmail.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, Fabien Chouteau <chouteau@adacore.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] slirp-related crash
Date: Mon, 13 Feb 2012 22:01:10 +0100 [thread overview]
Message-ID: <4F397A16.2020902@web.de> (raw)
In-Reply-To: <CA+wH294yhcappfe=gBgw4MqvHX9zpUNZzre5dia+K6bTHfR99Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
On 2012-02-13 21:43, Alex Bradbury wrote:
> On 13 February 2012 19:35, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>> I'm inclined to suggest a slirp rewrite (base support, not all features
>> at once) as a GSOC project. QEMU really deserves something better.
>
> Would it be feasible to adopt uip from kvm tool instead?
>
> https://github.com/penberg/linux-kvm/tree/master/tools/kvm/net/uip
> http://www.linux-kvm.org/wiki/images/c/c5/2011-forum-native-linux-kvm-tool.pdf
Surely a possible starting point. Or lwip, which also has v6. In any
case, there will be enough work to properly plug things into the QEMU
infrastructure and prepare them for the features slirp provides.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-02-13 21:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-12 18:34 [Qemu-devel] slirp-related crash Michael S. Tsirkin
2012-02-12 20:24 ` Jan Kiszka
2012-02-13 15:27 ` Zhi Yong Wu
2012-02-13 19:35 ` Jan Kiszka
2012-02-13 19:38 ` Jan Kiszka
2012-02-13 20:43 ` Alex Bradbury
2012-02-13 21:01 ` Jan Kiszka [this message]
2012-02-14 8:22 ` Stefan Hajnoczi
2012-02-14 10:14 ` Jan Kiszka
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=4F397A16.2020902@web.de \
--to=jan.kiszka@web.de \
--cc=asb@asbradbury.org \
--cc=chouteau@adacore.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=zwu.kernel@gmail.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).