From owner-freebsd-current@FreeBSD.ORG Thu Sep 24 16:34:38 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E158106566B for ; Thu, 24 Sep 2009 16:34:38 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-qy0-f176.google.com (mail-qy0-f176.google.com [209.85.221.176]) by mx1.freebsd.org (Postfix) with ESMTP id 5157F8FC14 for ; Thu, 24 Sep 2009 16:34:37 +0000 (UTC) Received: by qyk6 with SMTP id 6so16422qyk.3 for ; Thu, 24 Sep 2009 09:34:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=Z/tH8Wq54dI+M3ZPue3CA/AF26QWjiT12gE+ATmspME=; b=eLGvGmFKydIRF02QtDif58QbICNZRnd1a900sukN1V+SeO4aGLl5q5xsdFbR7pWvV6 53Uirg4YVVJZIHsSshSS3nA+SDmQ80Vjf+AFiOUQ5UfdQcGufqoHfNF8r/NJJ8GKlZtn 2mCz4YQTZo2oIAV3N9Bl/FIRjRTZWN+tAXRnk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=hrkKHatMqv2FQgUN47Rcr+8Rl9OOEcNeqGJgGcV2Vvcs+W20ajVyQOCM3fJNo3dLsY NueCGWqQKu3cNfWgu/cRXK1LGniYgt0M6XEfDTRqiUkcLdveDSMyay5ThZQwpcvuUFs9 tHQbZojqyR9aRlJuFKqSUqBZ0jCYAWIY924GE= Received: by 10.224.48.4 with SMTP id p4mr3407834qaf.231.1253810077342; Thu, 24 Sep 2009 09:34:37 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id 7sm39002qwf.47.2009.09.24.09.34.33 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 24 Sep 2009 09:34:34 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Thu, 24 Sep 2009 09:33:49 -0700 From: Pyun YongHyeon Date: Thu, 24 Sep 2009 09:33:48 -0700 To: Rafal Jaworowski Message-ID: <20090924163348.GA5272@michelle.cdnetworks.com> References: <20090922235350.GB1520@michelle.cdnetworks.com> <97F7ED67-AB93-4897-893B-16D3B22F9EB3@semihalf.com> <4ABA2C08.3070504@semihalf.com> <20090923170852.GA1099@michelle.cdnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: Grzegorz Bernacki , current@freebsd.org Subject: Re: mge, mii/e1000phy 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: Thu, 24 Sep 2009 16:34:38 -0000 On Thu, Sep 24, 2009 at 05:27:46PM +0200, Rafal Jaworowski wrote: > > On 2009-09-23, at 19:08, Pyun YongHyeon wrote: > > >On Wed, Sep 23, 2009 at 04:09:12PM +0200, Grzegorz Bernacki wrote: > >>>>From: Pyun YongHyeon > >>>>Date: 23 wrze?nia 2009 01:53:50 CEST > >>>>To: Kristof Provost > >>>>Cc: current@freebsd.org > >>>>Subject: Re: mge, mii/e1000phy > >>>>Reply-To: pyunyh@gmail.com > >>>> > >>>>>- Forcing the mge driver to IFM_100_TX (in > >>>>>mge_set_port_serial_control) > >>>>>does work. The system manages to acquire a DHCP address. > >>>> > >>>>Would you also show me the output of "ifconfig -m mge0"? > >>>> > >>>>I'm not author of mge(4) so I'm not familiar with mge(4). But it > >>>>seems that mge(4) lacks link state change handler. Normally NICs > >>>>are required to reprogram MAC to match resolved speed/duplex/ > >>>>flow-control of link when it know it established a valid link which > >>>>is notified from mii(4). > >>> > >> > >>Hi, > >> > >>You are right. Link state change handler is missing in mge(4) > >>driver. It > >>is on our TODO list for this driver and will be implemented soon. > >> > > > >I've briefly looked over MV88F5182 opensource community > >programmer's user guide and found that ENQ bit of TQC register > >should be set again whenever link DOWN/UP event is detected which > >in turn may complicate the driver as it may have to reset its > >descriptor indexes. And I guess it's wrong to spin wait until link > >is established in mge_init_locked(). The datasheet says Rx checksum > >offloading capability but can't find more information for that. > >Another nice looking feature that lacks in mge(4) would be > >interrupt coalescing. And I guess interrupt coalescing feature > >would give better performance than polling(4). > > > Both interrupt coalescing and RX checksum calculation offload are > already supported by the driver. > Yeah, I found it. Thanks for the info. :-) > Rafal >