From owner-freebsd-current Sat Mar 3 19: 0:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 0180937B718; Sat, 3 Mar 2001 19:00:20 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.3/8.11.3) id f2432m742565; Sat, 3 Mar 2001 19:02:48 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200103040302.f2432m742565@troutmask.apl.washington.edu> Subject: Re: cvs commit: src/sys/kern kern_intr.c src/sys/sys interrupt.h In-Reply-To: "from John Baldwin at Mar 3, 2001 05:32:51 pm" To: John Baldwin Date: Sat, 3 Mar 2001 19:02:48 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > > without causing problems. However, it may be that a sleep mutex wouldn't be > but so evil. If desired I can whip up a patch to do that instead and see how > much worse it is. It would probably hurt lpr performance a bit unless the > ppbus was fixed to do its own multiplexing of the interrupt. > I get an instance panic if I start lpd, so I doubt you can make lpr performance any worse ;-) The printer is connected to the parallel port. On my work machine, lpd/lpr work fine, but the printer is connected via tcp/ip. I have a crash dump if you need it. Sources are from 2 Mar 01 at 2158 PST. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message