From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] jumbo frames: needing some help
Date: Fri, 19 Sep 2008 13:58:53 -0500 [thread overview]
Message-ID: <48D3F66D.2080507@codemonkey.ws> (raw)
In-Reply-To: <20080919193742.vp0rkod868o0g84o@imap.uni-ulm.de>
martin.rauh@uni-ulm.de wrote:
> Hello, everyone!
>
> Sorry for the inconvenience, but as a part of my diploma thesis, I am
> creating a virtual NIC for QEMU, in order to support a new cluster OS
> of the university. (Saving the overhead caused by emulating real
> hardware, it is not emulating an existing NIC.) Anyway, now it seems
> to be working correctly, except for handling jumbo frames, which I
> have to make available.
You would have to post your patch. We seem to be able to handle jumbo
frames nicely with virtio-net.
BTW, are you aware of virtio-net? It has all of the properties that you
are describing and it already exists for Linux and Windows.
Regards,
Anthony Liguori
> I connected two QEMU instances by -net socket,listen and -net
> socket,connect options and I can send and receive packets in the
> guests. If I'm sending a 9000 byte packet, or bigger than 4 kByte, it
> is received completely by the other instance, but then QEMU crashes.
>
> I didn't find an according bug in the code of my NIC.
> MTU of 127.0.0.1 is 16436...
>
> Is there something special that I have to take care of, dealing with
> jumbo frames? Unfortunately I'm no expert in networking...
>
> Thank you in advance!
>
> Regards,
>
> Martin Rauh.
>
>
>
>
next prev parent reply other threads:[~2008-09-19 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 17:37 [Qemu-devel] jumbo frames: needing some help martin.rauh
2008-09-19 18:58 ` Anthony Liguori [this message]
2008-09-20 20:29 ` Martin Rauh
2008-09-22 19:42 ` Anthony Liguori
2008-09-23 16:57 ` Martin Rauh
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=48D3F66D.2080507@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).