From: Rusty Russell <rusty@rustcorp.com.au>
To: Mark McLoughlin <markmc@redhat.com>
Cc: netdev <netdev@vger.kernel.org>,
virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH] virtio_net: large tx MTU support
Date: Thu, 27 Nov 2008 23:00:56 +1030 [thread overview]
Message-ID: <200811272300.58151.rusty@rustcorp.com.au> (raw)
In-Reply-To: <1227707891.9579.44.camel@blaa>
On Thursday 27 November 2008 00:28:11 Mark McLoughlin wrote:
> We don't really have a max tx packet size limit, so allow configuring
> the device with up to 64k tx MTU.
Hi Mark,
Just one comment: maybe we should be conservative and maybe limit to 1500 if
the host doesn't offer any of the GSO or MRG_RXBUF features?
Thanks,
Rusty.
next prev parent reply other threads:[~2008-11-27 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 13:58 [PATCH] virtio_net: large tx MTU support Mark McLoughlin
2008-11-26 23:28 ` David Miller
2008-11-27 12:30 ` Rusty Russell [this message]
2008-11-27 13:57 ` Mark McLoughlin
2008-11-28 0:22 ` Rusty Russell
2008-11-28 9:29 ` Mark McLoughlin
2008-12-01 4:02 ` Rusty Russell
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=200811272300.58151.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=markmc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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).