From owner-freebsd-hackers Mon Jun 29 12:19:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19692 for freebsd-hackers-outgoing; Mon, 29 Jun 1998 12:19:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from animaniacs.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA19676 for ; Mon, 29 Jun 1998 12:18:54 -0700 (PDT) (envelope-from jamie@itribe.net) Received: from localhost (jamie@localhost) by animaniacs.itribe.net (950413.SGI.8.6.12/950213.SGI.AUTOCF) via SMTP id PAA02592; Mon, 29 Jun 1998 15:18:17 -0400 Date: Mon, 29 Jun 1998 15:18:17 -0400 (EDT) From: Jamie Bowden To: "Ron G. Minnich" cc: hackers@FreeBSD.ORG Subject: Re: I2O In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 29 Jun 1998, Ron G. Minnich wrote: > at usenix last week the question of I2O came up. > > Don't worry about I2O. Look around: how many I2O motherboards do you see, > as compared to non-I2O motherboards? > > Look at it this way: you think microsoft is that interested in requiring > a second operating system (vxworks) to make NT go? > > I2O will be a footnote in a year or so. After that, it will be forgotten > and in 10 years someone else will reinvent the idea and learn the hard > way why it is a bad one (as I2O is itself a reinvention of old, bad ideas). Why is offloading IO a bad idea? Offloading video and 3D rendering work well, it's what drives 3dfx and it's competitors. Or am I missing something? My basic understanding of I2O is using a subprocessor to handle all IO, thus freeing up the main processor from doing things like waiting on interrupts and the like. -- Jamie Bowden Systems Administrator, iTRiBE.net If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message