From owner-freebsd-amd64@FreeBSD.ORG  Sat Nov 13 14:22:30 2004
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6089516A4CE; Sat, 13 Nov 2004 14:22:30 +0000 (GMT)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 4DE2E43D3F; Sat, 13 Nov 2004 14:22:30 +0000 (GMT)
	(envelope-from mux@freebsd.org)
Received: by elvis.mu.org (Postfix, from userid 1920)
	id 432165CA02; Sat, 13 Nov 2004 06:22:30 -0800 (PST)
Date: Sat, 13 Nov 2004 15:22:30 +0100
From: Maxime Henrion <mux@freebsd.org>
To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
Message-ID: <20041113142230.GC32839@elvis.mu.org>
References: <Pine.BSF.4.53.0411130037360.85716@e0-0.zab2.int.zabbadoz.net>
	<200411121739.40804.peter@wemm.org>
	<Pine.BSF.4.53.0411130912020.85716@e0-0.zab2.int.zabbadoz.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.BSF.4.53.0411130912020.85716@e0-0.zab2.int.zabbadoz.net>
User-Agent: Mutt/1.4.2.1i
cc: FreeBSD current mailing list <freebsd-current@freebsd.org>
cc: FreeBSD amd64 mailing list <freebsd-amd64@freebsd.org>
Subject: Re: [PATCH] if_sk(4) rx/tx "hangs"
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Nov 2004 14:22:30 -0000

Bjoern A. Zeeb wrote:
> On Fri, 12 Nov 2004, Peter Wemm wrote:
> 
> > > Try something less CPU intensive like /dev/zero :)
> >
> > I think he was saying he created a 1GB file from the contents
> > of /dev/urandom and then timed the transfer of this over 100Mbit/sec
> > link.
> 
> that's it but I had been to lazy to tell you the whole dd story in te
> middle of the night.
> 
> I preffer random data when sometimes testing over ssh all zero get's
> easily compressed ;)
> 
> 
> > Anyway, the point was that it worked!  Could the problem with the K8V SE
> > really be as simple as we've been hardcoding 128K of ram for a device
> > that only has 64K?
> 
> It's not directly a matter of the K8V SE.
> 
> It's the 88E8001 (but at least my K8V SE deluxe has this one acording
> to the PN from VPD data).
> The 88E8010 already has 128k according to the pdf mentioned in my diff.
> 
> 
> Anyone actually tested it ? Mine still seems to be fine after the
> night.

I have this exact model (skc0: PN: Yukon 88E8001) in my work computer.
I had to use another NIC since this once was constantly wedging when
sending too much data.  I'll give this patch a try on Monday and let you
know.

Cheers,
Maxime