From owner-freebsd-hackers Sun Feb 21 4:38:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [208.221.12.98]) by hub.freebsd.org (Postfix) with ESMTP id B0210118BF for ; Sun, 21 Feb 1999 04:38:13 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id EAA12927; Sun, 21 Feb 1999 04:35:00 -0800 (PST) Message-Id: <199902211235.EAA12927@implode.root.com> To: Luigi Rizzo Cc: wpaul@skynet.ctr.columbia.edu, hackers@FreeBSD.ORG Subject: Re: How to handle jumbo etherney frames In-reply-to: Your message of "Sun, 21 Feb 1999 11:01:57 +0100." <199902211001.LAA13773@labinfo.iet.unipi.it> From: David Greenman Reply-To: dg@root.com Date: Sun, 21 Feb 1999 04:35:00 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> The jumbo frames are only useful if you also have VLAN support, which we >> don't have currently. We also need support for large mbuf clusters; this > >hmmm i don't get this -- why is this related to VLAN ? Because most ethernets consist of a mix of hosts that don't have jumbo frame capability. If you use jumbo frames without VLANs, then ALL hosts must support jumbo frames (and I think would also have to be gigabit ethernet connected since jumbo frames weren't supported in 802.3...although I'm assuming that the gigabit spec allows for jumbo frames, which may be a bad assumption on my part). -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message