From owner-freebsd-current@FreeBSD.ORG Fri Dec 12 03:56:33 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87E681065670 for ; Fri, 12 Dec 2008 03:56:33 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.237]) by mx1.freebsd.org (Postfix) with ESMTP id 4894B8FC17 for ; Fri, 12 Dec 2008 03:56:33 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1184391rvf.43 for ; Thu, 11 Dec 2008 19:56:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=slD0A7YeehrIAJuYQJ635f2wbvqiOJ7xWqFrbO6YEe0=; b=vf6FN3nev+RlxH8Cyn9uV0KPKKZQQi0fyoBb8HRIX9MZC1KQ2059+7PpUW787SIyhE 3c+Dm38BoOlPCEVVAGsGKad/Lq9DRmOJatPZapy780p3zYL/DBYafnetJ6arDR31WAxp 5I8yBswRbvdbrDFrx7cYAUVrdS/IB1WtkdjCw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=joEdtYrIFveizz+8fCtBz1So7JI7w/xfcVRgzeFOcNCvKRiMO9mJKsNIsU3PDhQ4zg EJkGc6IsOOhjamfTBxdjjJ9Ul8GTf/j12Yln67PMhWQbnl5miyrMTCA0NEgYvHWEInQR P83QRxyXVPdGJxqN1Pko+eSKWQB2Yr+oRuN60= Received: by 10.140.208.17 with SMTP id f17mr1655813rvg.261.1229054192861; Thu, 11 Dec 2008 19:56:32 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id f42sm1689876rvb.7.2008.12.11.19.56.30 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 11 Dec 2008 19:56:32 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id mBC3uP2r047650 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Dec 2008 12:56:25 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id mBC3uPVb047649; Fri, 12 Dec 2008 12:56:25 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 12 Dec 2008 12:56:25 +0900 From: Pyun YongHyeon To: Josh Carroll Message-ID: <20081212035625.GN46707@cdnetworks.co.kr> References: <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> <8cb6106e0812111951k18f4663ck2121b550dfe57322@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8cb6106e0812111951k18f4663ck2121b550dfe57322@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: Steve Franks , current-list freebsd Subject: Re: Call for testers: Atheros AR8121(L1E)/AR8113/AR8114(L2E) ethernet X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2008 03:56:33 -0000 On Thu, Dec 11, 2008 at 10:51:23PM -0500, Josh Carroll wrote: > > 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? > Yes, but msk(4) had hacks in e100phy(4) to enable flow-controls. I don't want to add these hacks to all other drivers in tree. > Thanks, I guess I'll stick with the em(4) PCI card, at least until I > can get a PCI-E em(4). :) > > Josh -- Regards, Pyun YongHyeon