From owner-cvs-all@FreeBSD.ORG  Mon Jul 26 14:46:04 2004
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Delivered-To: cvs-all@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4E54416A4CE; Mon, 26 Jul 2004 14:46:04 +0000 (GMT)
Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 47F0743D62; Mon, 26 Jul 2004 14:46:04 +0000 (GMT)
	(envelope-from yar@FreeBSD.org)
Received: from repoman.freebsd.org (localhost [127.0.0.1])
	by repoman.freebsd.org (8.12.11/8.12.11) with ESMTP id i6QEk468087219;
	Mon, 26 Jul 2004 14:46:04 GMT
	(envelope-from yar@repoman.freebsd.org)
Received: (from yar@localhost)
	by repoman.freebsd.org (8.12.11/8.12.11/Submit) id i6QEk4uC087218;
	Mon, 26 Jul 2004 14:46:04 GMT
	(envelope-from yar)
Message-Id: <200407261446.i6QEk4uC087218@repoman.freebsd.org>
From: Yar Tikhiy <yar@FreeBSD.org>
Date: Mon, 26 Jul 2004 14:46:04 +0000 (UTC)
To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org,
	cvs-all@FreeBSD.org
X-FreeBSD-CVS-Branch: HEAD
Subject: cvs commit: src/sys/net if_vlan.c
X-BeenThere: cvs-all@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the entire tree <cvs-all.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-all>,
	<mailto:cvs-all-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-all>
List-Post: <mailto:cvs-all@freebsd.org>
List-Help: <mailto:cvs-all-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-all>,
	<mailto:cvs-all-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2004 14:46:04 -0000

yar         2004-07-26 14:46:04 UTC

  FreeBSD src repository

  Modified files:
    sys/net              if_vlan.c 
  Log:
  Stop tinkering with the parent's VLAN_MTU capability.
  Now it is user-controlled through ifconfig(8).
  
  The former ``automagic'' way of operation created more
  trouble than good.  First, VLAN_MTU consumers other than
  vlan(4) had appeared, e.g., ng_vlan(4).  Second, there was
  no way to disable VLAN_MTU manually if it were causing
  trouble, e.g., data corruption.
  
  Dropping the ``automagic'' should be completely invisible
  to the user since
  a) all the drivers supporting VLAN_MTU
  have it enabled by default, and in the first place
  b) there is only one driver that can really toggle VLAN_MTU
  in the hardware under its control (it's fxp(4), to which
  I added VLAN_MTU controls to illustrate the principle.)
  
  Revision  Changes    Path
  1.72      +7 -27     src/sys/net/if_vlan.c