Date: Thu, 11 Dec 2008 22:51:23 -0500 From: "Josh Carroll" <josh.carroll@gmail.com> To: pyunyh@gmail.com Cc: Steve Franks <bahamasfranks@gmail.com>, current-list freebsd <freebsd-current@freebsd.org> Subject: Re: Call for testers: Atheros AR8121(L1E)/AR8113/AR8114(L2E) ethernet Message-ID: <8cb6106e0812111951k18f4663ck2121b550dfe57322@mail.gmail.com> In-Reply-To: <20081212034042.GL46707@cdnetworks.co.kr> References: <4910C055.8000505@janh.de> <20081203090658.GJ9639@cdnetworks.co.kr> <37502393@bb.ipt.ru> <20081206023016.GF22093@cdnetworks.co.kr> <539c60b90812081127s4ffb509fnea9d44d4298da666@mail.gmail.com> <8cb6106e0812081252j2b0c8e78g4dcecf8d3770c269@mail.gmail.com> <8cb6106e0812101745l54b23a08k7fbeddeb605f88ea@mail.gmail.com> <20081212020539.GI46707@cdnetworks.co.kr> <8cb6106e0812111923l15f1f715g6f20f5925e1d471a@mail.gmail.com> <20081212034042.GL46707@cdnetworks.co.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
> I guess it's caused by flow-control frames. > The flow-control feature is disabled in most drivers as mii(4) > layer still lacks the feture. ale(4) has flow-control support code > but it is in disabled state. When mii(4) is ready to handle > flow-controls ale(4) may work better. > em(4) does not rely on mii(4) layer so it implemented flow-controls > in driver. You can check flow-control satus of em(4) with > "sysctl dev.em.0.stats=1"(See XON/XOFF). Hmm, any idea why my previous motherboard (P5K-E) which had an msk(4) worked ok without the stuttering for this streaming? I believe it relies on mii as well, right? Thanks, I guess I'll stick with the em(4) PCI card, at least until I can get a PCI-E em(4). :) Josh
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8cb6106e0812111951k18f4663ck2121b550dfe57322>