From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10070 invoked by alias); 23 Apr 2004 16:29:34 -0000 Mailing-List: contact libc-hacker-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-hacker-owner@sources.redhat.com Received: (qmail 10046 invoked from network); 23 Apr 2004 16:29:33 -0000 Received: from unknown (HELO myware.akkadia.org) (24.221.190.179) by sources.redhat.com with SMTP; 23 Apr 2004 16:29:33 -0000 Received: from redhat.com (drepper@myware.akkadia.org [192.168.7.70]) (authenticated bits=0) by myware.akkadia.org (8.12.11/8.12.11) with ESMTP id i3NGT0pU023437; Fri, 23 Apr 2004 09:29:00 -0700 Message-ID: <4089444B.2060906@redhat.com> Date: Fri, 23 Apr 2004 16:29:00 -0000 From: Ulrich Drepper Organization: Red Hat, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a) Gecko/20040422 MIME-Version: 1.0 To: bmark@us.ibm.com CC: Glibc hackers Subject: Re: AIO work in librt References: In-Reply-To: X-Enigmail-Version: 0.83.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SW-Source: 2004-04/txt/msg00087.txt.bz2 Mark Brown wrote: > We are thinking about making this work in librt (and submitting it, of > course). Making what work? RHEL ships with some support for kernel aio already. This code (or more specifically: the kernel side) is not yet in sufficient shape to be accepted. That's what's keeping it back. The librt side should be done for the current kernel aio approach which is everything but sane. So the task is to design an implement a workable aio implementation in the kernel and I haven't seen anything like this lately. -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖