Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 4 May 2008 15:29:42 -0700
From:      "Jack Vogel" <jfvogel@gmail.com>
To:        "Oleksandr Samoylyk" <oleksandr@samoylyk.sumy.ua>
Cc:        freebsd-net@freebsd.org, mike@sentex.net
Subject:   Re: Troubles with em on FreeBSD 7
Message-ID:  <2a41acea0805041529j5d4dd2f7x5e07a8d6d2eb89b6@mail.gmail.com>
In-Reply-To: <481E338D.6040706@samoylyk.sumy.ua>
References:  <481C84B7.6020205@samoylyk.sumy.ua> <bibs14perk47snkpg8fu691kjkc42gh6m2@4ax.com> <481E338D.6040706@samoylyk.sumy.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, May 4, 2008 at 3:07 PM, Oleksandr Samoylyk
<oleksandr@samoylyk.sumy.ua> wrote:
> mike@sentex.net wrote:
>
> >
> > A new version of the em drivers went into the tree Friday.
> >
> >
> > > dev.em.0.%desc: Intel(R) PRO/1000 Network Connection Version - 6.7.3
> > >
> >
> > dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 6.9.0
> > dev.em.0.%driver: em
> > dev.em.0.%location: slot=0 function=0
> > dev.em.0.%pnpinfo: vendor=0x8086 device=0x108c subvendor=0x15d9
> > subdevice=0x108c class=0x020000
> > dev.em.0.%parent: pci13
> > dev.em.0.debug: -1
> > dev.em.0.stats: -1
> > dev.em.0.rx_int_delay: 0
> > dev.em.0.tx_int_delay: 66
> > dev.em.0.rx_abs_int_delay: 66
> > dev.em.0.tx_abs_int_delay: 66
> > dev.em.0.rx_processing_limit: 100
> >
>
>  I tried both:
>
>  - new drivers: 6.9.0
>  - rx_processing_limit: 100
>
>  Result the same :(
>
>
>
> > Also, post some of the stats.  Do a sysctl -w dev.em.1.stats=1
> > to all of your em nics
> >
>
>  em0: Excessive collisions = 0
>  em0: Sequence errors = 0
>  em0: Defer count = 0
>  em0: Missed Packets = 434970
>  em0: Receive No Buffers = 290593
>  em0: Receive Length Errors = 0
>  em0: Receive errors = 0
>  em0: Crc errors = 0
>  em0: Alignment errors = 0
>  em0: Collision/Carrier extension errors = 0
>  em0: RX overruns = 2929
>  em0: watchdog timeouts = 0
>  em0: XON Rcvd = 0
>  em0: XON Xmtd = 0
>  em0: XOFF Rcvd = 0
>  em0: XOFF Xmtd = 0
>  em0: Good Packets Rcvd = 64182304
>  em0: Good Packets Xmtd = 84277659
>  em0: TSO Contexts Xmtd = 832
>  em0: TSO Contexts Failed = 0
>
>
>  em1: Excessive collisions = 0
>  em1: Sequence errors = 0
>  em1: Defer count = 0
>  em1: Missed Packets = 0
>  em1: Receive No Buffers = 0
>  em1: Receive Length Errors = 0
>  em1: Receive errors = 0
>  em1: Crc errors = 0
>  em1: Alignment errors = 0
>  em1: Collision/Carrier extension errors = 0
>  em1: RX overruns = 0
>  em1: watchdog timeouts = 0
>  em1: XON Rcvd = 0
>  em1: XON Xmtd = 0
>  em1: XOFF Rcvd = 0
>  em1: XOFF Xmtd = 0
>  em1: Good Packets Rcvd = 62431510
>  m1: Good Packets Xmtd = 55466567
>  em1: TSO Contexts Xmtd = 0
>
>  em1: TSO Contexts Failed = 0
>
>
> > And are you using gigabit or fastE. If fastE, try disabling TSO as
> > some people have said they have problems with it at 100Mb.
> >
>
>  I'm on GgE. Disabling TSO doesn't help as well.

You are running out of RX side resources, did you say this
was UDP? I'm guessing upping your mbuf pool at least, I
can't think of something in driver-wise that would help.

If you have this same load going into a different nic, or
different os (like say Linux) can it manage?

This will take some thought, I'm not sure off the top of
my head here.

Jack



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