From owner-freebsd-net  Fri Jun 28 10:43:34 2002
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6B00C37B40E
	for <net@FreeBSD.ORG>; Fri, 28 Jun 2002 10:43:06 -0700 (PDT)
Received: from patrocles.silby.com (d186.as9.nwbl0.wi.voyager.net [169.207.133.252])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CF81243E09
	for <net@FreeBSD.ORG>; Fri, 28 Jun 2002 10:42:55 -0700 (PDT)
	(envelope-from silby@silby.com)
Received: from patrocles.silby.com (localhost [127.0.0.1])
	by patrocles.silby.com (8.12.4/8.12.4) with ESMTP id g5SHjVcv073203;
	Fri, 28 Jun 2002 12:45:31 -0500 (CDT)
	(envelope-from silby@silby.com)
Received: from localhost (silby@localhost)
	by patrocles.silby.com (8.12.4/8.12.4/Submit) with ESMTP id g5SHjUYA073200;
	Fri, 28 Jun 2002 12:45:31 -0500 (CDT)
X-Authentication-Warning: patrocles.silby.com: silby owned process doing -bs
Date: Fri, 28 Jun 2002 12:45:30 -0500 (CDT)
From: Mike Silbersack <silby@silby.com>
To: Luigi Rizzo <rizzo@icir.org>
Cc: net@FreeBSD.ORG
Subject: Junior Kernel hacker task? <g> Re: interface stalling on tx ?
In-Reply-To: <20020628005253.B55603@iguana.icir.org>
Message-ID: <20020628124055.L72733-100000@patrocles.silby.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-net.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-net>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-net>
X-Loop: FreeBSD.org


On Fri, 28 Jun 2002, Luigi Rizzo wrote:

> ok, i think this is exactly the problem, and "conservative" is
> an understatement, I would call that plain broken :)
>
> Your fix seems the correct way to handle the problem,
> I wonder if there is an easy way to put something like
> this in a generic procedure (such as ether_output_frame)
> that is called by all drivers instead of relying on the
> individual drivers to do the right thing each one in its
> own way...

I think that it would probably be easier to go and fix many of the network
drivers than to abstract the watchdog timer more.

<This is the point where silby offers to make the change to all network
card drivers, then tragically realizes that he has other stuff he should
handle first.>

If some junior kernel hacker wants a chance to write up some simple
patches, this would be a good project.  Of course, this also means that
you must find someone with a network card for each driver you patch and
have them ensure that the changes do not cause any problems.  Then send
the patches to me, and I'll get them committed.

Mike "Silby" Silbersack


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message