cvs commit: src/sys/conf files src/sys/dev/netif/bce if_bce.c src/sys/dev/netif/bge if_bge.c src/sys/dev/netif/em if_em.c src/sys/dev/netif/nfe if_nfe.c src/sys/dev/netif/nge if_nge.c src/sys/dev/netif/re if_re.c src/sys/dev/netif/stge if_stge.c ...

[Sepherosa Ziehau]

sephe       2008/03/10 03:47:58 PDT

DragonFly src repository

  Modified files:
    sys/conf             files 
    sys/dev/netif/bce    if_bce.c 
    sys/dev/netif/bge    if_bge.c 
    sys/dev/netif/em     if_em.c 
    sys/dev/netif/nfe    if_nfe.c 
    sys/dev/netif/nge    if_nge.c 
    sys/dev/netif/re     if_re.c 
    sys/dev/netif/stge   if_stge.c 
    sys/dev/netif/ti     if_ti.c 
    sys/dev/netif/txp    if_txp.c 
    sys/dev/netif/vge    if_vge.c 
    sys/net/vlan         if_vlan.c if_vlan_var.h 
    sys/sys              mbuf.h 
  Added files:
    sys/net/vlan         if_vlan_ether.c 
  Log:
  - Embed ether vlan tag in mbuf packet header.  Add an mbuf flag to mark that
    this field is valid.
  - Hide ifvlan after the above change; drivers support hardware vlan tagging
    only need to check ether_vlantag in mbuf packet header.
  - Convert all drivers that support hardware vlan tagging to use vlan tag field
    in mbug packet header.
  
  Obtained-from: FreeBSD
  
  Change the vlan/parent serializer releasing/holding sequences into mbuf
  dispatching.  There are several reasons to do so:
  - Avoid excessive vlan interface serializer releasing/holding
  - Touching parent interface if_snd without holding parent's serializer is
    unsafe
  - vlan's parent may disappear or be changed after vlan's serializer is released
  
  # This dispatching could be further optimized by packing all mbufs into one
  # netmsg using m_nextpkt to:
  # - Amortize netmsg sending cost
  # - Reduce the time that parent interface spends on serializer releasing/holding
  
  Revision  Changes    Path
  1.208     +1 -0      src/sys/conf/files
  1.2       +2 -6      src/sys/dev/netif/bce/if_bce.c
  1.89      +2 -8      src/sys/dev/netif/bge/if_bge.c
  1.64      +4 -9      src/sys/dev/netif/em/if_em.c
  1.18      +2 -8      src/sys/dev/netif/nfe/if_nfe.c
  1.45      +2 -8      src/sys/dev/netif/nge/if_nge.c
  1.37      +4 -8      src/sys/dev/netif/re/if_re.c
  1.3       +2 -9      src/sys/dev/netif/stge/if_stge.c
  1.49      +7 -14     src/sys/dev/netif/ti/if_ti.c
  1.46      +3 -5      src/sys/dev/netif/txp/if_txp.c
  1.6       +4 -9      src/sys/dev/netif/vge/if_vge.c
  1.28      +49 -79    src/sys/net/vlan/if_vlan.c
  1.4       +0 -22     src/sys/net/vlan/if_vlan_var.h
  1.46      +5 -1      src/sys/sys/mbuf.h


http://www.dragonflybsd.org/cvsweb/src/sys/conf/files.diff?r1=1.207&r2=1.208&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/netif/bce/if_bce.c.diff?r1=1.1&r2=1.2&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/netif/bge/if_bge.c.diff?r1=1.88&r2=1.89&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/netif/em/if_em.c.diff?r1=1.63&r2=1.64&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/netif/nfe/if_nfe.c.diff?r1=1.17&r2=1.18&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/netif/nge/if_nge.c.diff?r1=1.44&r2=1.45&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/netif/re/if_re.c.diff?r1=1.36&r2=1.37&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/netif/stge/if_stge.c.diff?r1=1.2&r2=1.3&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/netif/ti/if_ti.c.diff?r1=1.48&r2=1.49&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/netif/txp/if_txp.c.diff?r1=1.45&r2=1.46&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/dev/netif/vge/if_vge.c.diff?r1=1.5&r2=1.6&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/net/vlan/if_vlan.c.diff?r1=1.27&r2=1.28&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/net/vlan/if_vlan_var.h.diff?r1=1.3&r2=1.4&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/sys/mbuf.h.diff?r1=1.45&r2=1.46&f=u