From owner-freebsd-current Fri Dec 5 02:20:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA10630 for current-outgoing; Fri, 5 Dec 1997 02:20:33 -0800 (PST) (envelope-from owner-freebsd-current) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA10620 for ; Fri, 5 Dec 1997 02:20:26 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id CAA17239; Fri, 5 Dec 1997 02:15:07 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd017217; Fri Dec 5 02:14:57 1997 Date: Fri, 5 Dec 1997 02:12:34 -0800 (PST) From: Julian Elischer To: Poul-Henning Kamp cc: current@FreeBSD.ORG Subject: Re: weird current behaviour... In-Reply-To: <10662.881306559@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I don't remember the picture.. what were the drivers? On Fri, 5 Dec 1997, Poul-Henning Kamp wrote: > 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." >