From owner-freebsd-isp Wed Oct 16 16:08:14 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA13654 for isp-outgoing; Wed, 16 Oct 1996 16:08:14 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA13643 for ; Wed, 16 Oct 1996 16:08:07 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id JAA14547; Thu, 17 Oct 1996 09:07:44 +1000 (EST) Date: Thu, 17 Oct 1996 09:07:40 +1000 (EST) From: "Daniel O'Callaghan" To: Chris Peltier cc: "'freebsd-isp@FreeBSD.ORG'" Subject: Re: pppd reliability In-Reply-To: <96Oct16.082411edt.6151@netgate.iectech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 16 Oct 1996, Chris Peltier wrote: > Does anybody have any experience using pppd to run > dedicated 115K ppp links (ISDN application) on > 2.1.0 release. My main concern is reliability and > CPU loading experiences. I am considering 16550 > UART based boards and the Cyclades products. I use pppd (kernel-based ppp) with AST clones (16550s) and cyclades. Both work well, but I feel that the cyclades are a little better. A heavily loaded 486-33 with 20 busy links at 57600 on cy0, cy1 (ISA) consumes about 25% of CPU in servicing interrupts. Rule of thumb ratios indicates the same load would occupy about 3% of CPU on a P133. There is a now a driver for PCI-cy, but that is in -current, and not in 2.1.5R, I believe. Danny