From owner-freebsd-net@FreeBSD.ORG Tue Jun 11 02:27:42 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4432674B; Tue, 11 Jun 2013 02:27:42 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) by mx1.freebsd.org (Postfix) with ESMTP id 138E41459; Tue, 11 Jun 2013 02:27:42 +0000 (UTC) Received: by mail-pa0-f45.google.com with SMTP id bi5so4997414pad.18 for ; Mon, 10 Jun 2013 19:27:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=YzWsOcwQyVgR4UCLPnhWmNsc07ApTehMnBRLjwgvgpQ=; b=xGkewv/11Go2Bq5r8nhuwJwrgGcTi9sHGOI9vYmtQHUQqZrPSZir8iB/wHzSreKavn U77EALld14/Ew7zKvAg5PTR8wnTEZO1gBl2gEc/zrgG5eORYTjzDmyLwGehhjgY7hDGw zCynOivJ+k60YEqyYkQn9WlPMoUbYw/fowgoWCXIn1lKoLdjMMV5vutccvS5oBhSNxnw BpwQ9BDXwTqwi8RGKEIleSSUgQr15/px5HPoVy/92m3jkOqD++TGJQrlOSluD94yqGXs f0KrHFskRaJmVISTOoxEmjBh5LzhKTPyevbOs7CjLBPur0BxhWwsNhujp6n9bzEPsApI TbHg== X-Received: by 10.66.145.2 with SMTP id sq2mr16344004pab.2.1370917661909; Mon, 10 Jun 2013 19:27:41 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPSA id l4sm12504290pbo.6.2013.06.10.19.27.38 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 10 Jun 2013 19:27:40 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Tue, 11 Jun 2013 11:27:34 +0900 From: YongHyeon PYUN Date: Tue, 11 Jun 2013 11:27:34 +0900 To: "Mr. Clif" Subject: Re: misc/179033: [dc] dc ethernet driver seems to have issues with some multiport card and mother board combinations Message-ID: <20130611022734.GB1519@michelle.cdnetworks.com> References: <201305300113.r4U1DRGp089692@freefall.freebsd.org> <51A6CE52.20501@eugeneweb.com> <20130530051214.GA1530@michelle.cdnetworks.com> <201305300929.31872.jhb@freebsd.org> <51B62547.5000207@eugeneweb.com> <20130611002848.GA1519@michelle.cdnetworks.com> <51B67CCA.2010507@eugeneweb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51B67CCA.2010507@eugeneweb.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org, John Baldwin , yongari@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jun 2013 02:27:42 -0000 On Mon, Jun 10, 2013 at 06:26:34PM -0700, Mr. Clif wrote: > Is there any down side to using that dc fix in pfsense for now? If dc(4) works as expected there is no reason not to use memory BARs. Generally using memory BARs is more efficient. Many old PCI controllers used to have bugs with memory BARs so driver used safer I/O port BARs. > > Yes, I would like to have time to submit the cas bug as well. Maybe in > the next week but probably by august I hope. ;-) > Ok. > Thanks for your help, > Clif