From owner-freebsd-stable Tue May 1 8:30:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.bmi.net (smtp.bmi.net [204.57.191.31]) by hub.freebsd.org (Postfix) with ESMTP id 4B8D737B423 for ; Tue, 1 May 2001 08:30:46 -0700 (PDT) (envelope-from jmcoopr@webmail.bmi.net) Received: from webmail.bmi.net (dsl-154.bmi.net [207.173.60.230]) by smtp.bmi.net (Pro-8.9.3/Pro-8.9.3) with ESMTP id IAA11864; Tue, 1 May 2001 08:30:38 -0700 Message-ID: <3AEED69E.F6EC1EAD@webmail.bmi.net> Date: Tue, 01 May 2001 08:30:38 -0700 From: John Merryweather Cooper X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en-US, en, en-GB MIME-Version: 1.0 To: Peter Jeremy Cc: FreeBSD-STABLE Mailing List Subject: Re: problem with plip stealing clock References: <3AED84DB.8D241BCF@webmail.bmi.net> <20010501171807.M59150@gsmx07.alcatel.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy wrote: > > On 2001-Apr-30 08:29:31 -0700, John Merryweather Cooper wrote: > >While using my main workstation as a local FTP for my laptop over plip, > >I noticed that FreeBSD was losing track of time at a prodigious rate. > > PLIP receives/transmits each IP packet inside a loop at splhigh(). > If either system is slow, or the MTU is too high, the time taken to > transfer each packet can exceed 1 tick - meaning that clock interrupt > is lost. Other PIO peripherals (ethernet or disk) will aggravate the > problem. I suspect transfering between a AMD Duron 700 and an Intel 386SX/20 qualifies . . . :) Couldn't the plip interface arbitrate this though by driving it's "bus" cycle at the pace of the slowest system? I'm sure, in practice, that the rarest use of plip is between two machines of nearly equal CPU speed. Probably, my use is fairly typical. If my damn laptop had a network port, I'd use that--but the Token Ring 16/4 Adapter seems as rare a gold for my ancient AST Premium Exec 386SX/20 . . . :) Probably wouldn't work with FreeBSD anyway . . . bummer. > I did have the problem with PLIP between my 386 laptop and 486 desktop > until I reduced the MTU to 512. Anything "magical" about 512 (or is lower better here). If lower is better, how low can I go (I guess I'll find out). > Have you considered using a PPP link running at 115.2kbps instead? > You will find it a lot more CPU friendly. Yes. Not looking forward to buying yet another single-purpose cable. The null modem I have doesn't seem to do the trick anymore. > Peter > jmc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message