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>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH] virtio_net: large tx MTU support
Date: Fri, 28 Nov 2008 10:52:33 +1030 [thread overview]
Message-ID: <200811281052.33474.rusty@rustcorp.com.au> (raw)
In-Reply-To: <1227794225.24571.36.camel@blaa>
On Friday 28 November 2008 00:27:05 Mark McLoughlin wrote:
> Hi Rusty,
>
> On Thu, 2008-11-27 at 23:00 +1030, Rusty Russell wrote:
> > 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?
>
> That was actually what I was going to do until I thought about it a bit
> more and discussed it with Herbert.
>
> The virtio_net MTU only affects the transmit path, so there shouldn't be
> any issue with a host that doesn't support those features.
Not quite what I meant. A minimal host can reasonably expect ethernet-fitting
packets. If it supports GSO of course it must handle larger ones. Otherwise
we should add YA feature bit or even a max-mtu field.
So, I was thinking something like this over your patch (I also removed the
used-once MAX and MIN definitions; I dislike gratuitous indirection):
diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
--- a/drivers/net/virtio_net.c
+++ b/drivers/net/virtio_net.c
@@ -480,26 +480,24 @@ static struct ethtool_ops virtnet_ethtoo
.set_sg = ethtool_op_set_sg,
};
-#define MIN_MTU 68
-#define MAX_MTU 65535
-
static int virtnet_change_mtu(struct net_device *dev, int new_mtu)
{
struct virtnet_info *vi = netdev_priv(dev);
int max_mtu;
- /* Only allow a large MTU if we know we have a chance
- * of also supporting that MTU on the receive side. */
- if (vi->mergeable_rx_bufs || vi->big_packets)
- max_mtu = MAX_MTU;
+ /* A host which can handle GSO must handle large packets. */
+ if (virtio_has_feature(vi->vdev, VIRTIO_NET_F_GSO)
+ || virtio_has_feature(vi->vdev, VIRTIO_NET_F_HOST_TSO4)
+ || virtio_has_feature(vi->vdev, VIRTIO_NET_F_HOST_TSO6)
+ || virtio_has_feature(vi->vdev, VIRTIO_NET_F_HOST_UFO))
+ max_mtu = 65535;
else
max_mtu = ETH_DATA_LEN;
- if (new_mtu < MIN_MTU || new_mtu > max_mtu)
+ if (new_mtu < 68 || new_mtu > max_mtu)
return -EINVAL;
dev->mtu = new_mtu;
-
return 0;
}
next prev parent reply other threads:[~2008-11-28 0:22 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
2008-11-27 13:57 ` Mark McLoughlin
2008-11-28 0:22 ` Rusty Russell [this message]
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=200811281052.33474.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=herbert@gondor.apana.org.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).