From: Samuel Thibault <samuel.thibault@gnu.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Chris Heinze" <c.heinze@precibake.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] slirp, incoming packets get truncated
Date: Mon, 9 Sep 2019 12:59:49 +0200 [thread overview]
Message-ID: <20190909105949.45jdxvzwusonn327@function> (raw)
In-Reply-To: <47bad7a1-8fae-b464-7c74-b458d02a6174@redhat.com>
Hello,
Philippe Mathieu-Daudé, le lun. 09 sept. 2019 12:51:23 +0200, a ecrit:
> Anyhow, if you plan to properly (with your S-o-b) commit your patch to
> the libslirp repository,
Actually the libslirp repository already has something there. Since
IPv4/6 have a maximum of 64KB packets, it just allocates that size
on the stack, whîch is simpler in the end. Also it makes mru/mtu
configurable, we will be able to plug that into qemu once released.
Samuel
prev parent reply other threads:[~2019-09-09 11:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 15:02 [Qemu-devel] slirp, incoming packets get truncated Chris Heinze
2019-09-06 9:59 ` Samuel Thibault
2019-09-06 10:54 ` Chris Heinze
2019-09-06 11:14 ` Samuel Thibault
2019-09-07 23:29 ` Samuel Thibault
2019-09-09 10:35 ` Chris Heinze
2019-09-09 10:51 ` Philippe Mathieu-Daudé
2019-09-09 10:59 ` Samuel Thibault [this message]
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=20190909105949.45jdxvzwusonn327@function \
--to=samuel.thibault@gnu.org \
--cc=c.heinze@precibake.com \
--cc=marcandre.lureau@redhat.com \
--cc=philmd@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).