From owner-kaio@oss.sgi.com Fri Aug 25 20:24:02 2000 Received: by oss.sgi.com id ; Fri, 25 Aug 2000 20:23:43 -0700 Received: from mb07.swip.net ([193.12.122.211]:49135 "EHLO mb07.swip.net") by oss.sgi.com with ESMTP id ; Fri, 25 Aug 2000 20:23:12 -0700 Received: from henrik.localdomain (d212-151-176-27.swipnet.se [212.151.176.27]) by mb07.swip.net (8.8.8/8.8.8) with ESMTP id FAA24730 for ; Sat, 26 Aug 2000 05:21:55 +0200 (MET DST) Received: from henrik.localdomain (localhost [127.0.0.1]) by henrik.localdomain (8.9.3/8.9.3) with SMTP id FAA08247 for ; Sat, 26 Aug 2000 05:24:03 +0200 Message-ID: <39A73852.184F4131@hem.passagen.se> Date: Sat, 26 Aug 2000 05:24:02 +0200 From: Henrik Nordstrom X-Mailer: Mozilla 3.01 (X11; I; Linux 2.2.16-3 i586) MIME-Version: 1.0 To: kaio@oss.sgi.com Subject: KAIO and Linux-2.4.0-testX Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-kaio@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;kaio-outgoing Hi. I noticed that the KAIO patch set hasn't been maintained for quite a wile, and there seems to be very little discussion around it. Are looking into using KAIO for a I/O intensive task, and wonder two things a) Is there any known issues with running the KAIO patches on newer kernels? b) How hard would it be to implement open() and close() as KAIO operations? From what I understand only the stantard POSIX operations are implemented, but for some applications open() is a major bottleneck in blocking. -- Henrik Nordstrom