Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Oct 2010 18:43:06 +0000 (UTC)
From:      Pyun YongHyeon <yongari@FreeBSD.org>
To:        cvs-src-old@freebsd.org
Subject:   cvs commit: src/sys/dev/bge if_bge.c if_bgereg.h
Message-ID:  <201010081843.o98IhN1O001718@repoman.freebsd.org>

next in thread | raw e-mail | index | archive | help
yongari     2010-10-08 18:43:06 UTC

  FreeBSD src repository

  Modified files:        (Branch: RELENG_8)
    sys/dev/bge          if_bge.c if_bgereg.h 
  Log:
  SVN rev 213593 on 2010-10-08 18:43:06Z by yongari
  
  MFC r212061,212065,212302:
  r212061:
    Split common parent DMA tag into ring DMA tag and TX/RX mbuf DMA
    tag. All controllers that are not BCM5755 or higher have 4GB
    boundary DMA bug. Previously bge(4) used 32bit DMA address to
    workaround the bug(r199670). However this caused the use of bounce
    buffers such that it resulted in poor performance for systems which
    have more than 4GB memory. Because bus_dma(9) honors boundary
    restriction requirement of DMA tag for dynamic buffers, having a
    separate TX/RX mbuf DMA tag will greatly reduce the possibility of
    using bounce buffers. For DMA buffers allocated with
    bus_dmamem_alloc(9), now bge(4) explicitly checks whether the
    requested memory region crossed the boundary or not.
    With this change, only the DMA buffer that crossed the boundary
    will use 32bit DMA address. Other DMA buffers are not affected as
    separate DMA tag is created for each DMA buffer.
    Even if 32bit DMA address space is used for a buffer, the chance to
    use bounce buffer is still very low as the size of buffer is small.
    This change should eliminate most usage of bounce buffers on
    systems that have more than 4GB memory.
  
    More correct fix would be teaching bus_dma(9) to honor boundary
    restriction for buffers created with bus_dmamem_alloc(9) but it
    seems that is not easy.
  
    While I'm here cleanup bge_dma_map_addr() and remove unnecessary
    member variables in bge_dmamap_arg structure.
  
    Tested by:    marcel
  
  r212065:
    Handle PAE case correctly. You cannot effectively specify a 4GB
    boundary in PAE case so use a 2GB boundary for PAE as suggested by
    jhb.
  
    Pointed out by:       jhb
    Reviewed by:  jhb
  
  r212302:
    Make sure to create DMA'able memory for statistics block. This was
    missed in r212061 and it caused crashes for 570x controllers as
    controller DMAed statistics to physical address 0.
  
    Reported by:  kan
  
  Revision    Changes    Path
  1.226.2.32  +154 -238  src/sys/dev/bge/if_bge.c
  1.83.2.16   +11 -5     src/sys/dev/bge/if_bgereg.h



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201010081843.o98IhN1O001718>