From owner-freebsd-hackers Sat Nov 1 21:52:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA01600 for hackers-outgoing; Sat, 1 Nov 1997 21:52:48 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from word.smith.net.au ([202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA01591 for ; Sat, 1 Nov 1997 21:52:38 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id QAA00293; Sun, 2 Nov 1997 16:18:54 +1030 (CST) Message-Id: <199711020548.QAA00293@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jamil J. Weatherbee" cc: hackers@freebsd.org, dufault@hda.com Subject: Re: Strategy Routines In-reply-to: Your message of "Sat, 01 Nov 1997 21:36:30 -0800." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Nov 1997 16:18:53 +1030 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk (Peter, are you on -hackers?) > Ok, so say I am doing outb(), one bang after the other. Since timo can > sleep up to 1/100 of a second. What would be a good "packet size" (i.e. > number of outb() to limit myself to in a loop. I still have to wonder why you would want to do this in the first place. However I'd take two separate approaches: - sequenced output, use tsleep() between output values. - fast output, limit yourself to N bytes of output, then return from the write() call with a short count. No timeouts, no sleeping, no blocking for unreasonable periods. I'd perhaps limit to 512 bytes per write. mike