From owner-freebsd-current  Thu Dec  4 23:24:51 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id XAA25951
          for current-outgoing; Thu, 4 Dec 1997 23:24:51 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA25934
          for <current@FreeBSD.ORG>; Thu, 4 Dec 1997 23:24:46 -0800 (PST)
          (envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1])
	by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id IAA10664;
	Fri, 5 Dec 1997 08:22:39 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: Julian Elischer <julian@whistle.com>
cc: current@FreeBSD.ORG
Subject: Re: weird current behaviour... 
In-reply-to: Your message of "Thu, 04 Dec 1997 17:45:56 PST."
             <34875CD4.7566F4CF@whistle.com> 
Date: Fri, 05 Dec 1997 08:22:39 +0100
Message-ID: <10662.881306559@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

In message <34875CD4.7566F4CF@whistle.com>, Julian Elischer writes:
>All the fast ones only have interrupt context processing.
>the slow ones have a userland context. (the ping process)
>The rc456 programs are finishing up their quantum before allowing the 
>ping to run and recieve the response.


Wrong.  If I ping C from A it works fine.  If I ping B from A it
works fine.  If I ping D or E from A it works badly.

In all cases the path is the same...

I agree that it is somehow related to context switching, but how ?

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."