From owner-freebsd-hackers Wed Jun 19 22:50:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA19426 for hackers-outgoing; Wed, 19 Jun 1996 22:50:49 -0700 (PDT) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA19414 for ; Wed, 19 Jun 1996 22:50:43 -0700 (PDT) Received: from seagull.rtd.com (seagull.rtd.com [198.102.68.2]) by mail.barrnet.net (8.7.5/MAIL-RELAY-LEN) with ESMTP id WAA09630 for ; Wed, 19 Jun 1996 22:50:29 -0700 (PDT) Received: (from dgy@localhost) by seagull.rtd.com (8.7.5/1.2) id WAA09980 for freebsd-hackers@freefall.cdrom.com; Wed, 19 Jun 1996 22:46:33 -0700 (MST) From: Don Yuniskis Message-Id: <199606200546.WAA09980@seagull.rtd.com> Subject: Looking for cavemen... To: freebsd-hackers@freefall.FreeBSD.org (FreeBSD hackers) Date: Wed, 19 Jun 1996 22:46:33 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ...and other assorted dinosaurs! :> Hi! I'm looking for some ideas and suggestions regarding optimization strategies for a rewrite of my ("traditional") `mt' driver. In particular, algorithms that I can employ to schedule read/write/seek operations for the character and block devices. I suspect that these devices are a bit unique (spelled "frustrating") in their capabilities vs. their more contemporary counterparts. I've searched netspace and found very little "public" information in this area :-( Thanks! --don