X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id 7EB999DD441
	for <pgsql-hackers-postgresql.org@localhost.postgresql.org>;
	Tue, 29 Nov 2005 12:05:11 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 01494-03-3
	for <pgsql-hackers-postgresql.org@localhost.postgresql.org>;
	Tue, 29 Nov 2005 12:05:08 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from toad.mtbrook.bozemanpass.com (toad.mtbrook.bozemanpass.com
	[69.145.82.195])
	by postgresql.org (Postfix) with ESMTP id 69B769DCD22
	for <pgsql-hackers@postgresql.org>;
	Tue, 29 Nov 2005 11:42:11 -0400 (AST)
Received: from [69.145.82.253] (unknown [69.145.82.253])
	by toad.mtbrook.bozemanpass.com (Postfix) with ESMTP id 949CA11027B
	for <pgsql-hackers@postgresql.org>;
	Tue, 29 Nov 2005 07:42:16 -0800 (PST)
Message-ID: <438C76DA.4060801@boreham.org>
Date: Tue, 29 Nov 2005 08:42:18 -0700
From: David Boreham <david_list@boreham.org>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: pgsql-hackers@postgresql.org
Subject: Re: ice-broker scan thread
References: <Pine.LNX.4.58.0511282217470.13586@josh.db>
	<Pine.LNX.4.58.0511291429330.18112@linuxworld.com.au>
	<20051129110214.GA31333@svana.org>
In-Reply-To: <20051129110214.GA31333@svana.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0 required=5 tests=[AWL=0.000]
X-Spam-Score: 0
X-Spam-Level: 
X-Archive-Number: 200511/1478
X-Sequence-Number: 76760


>Unfortunatly I can't really test it at it's full potential because it
>uses glibc's default POSIX AIO which is *lame*. No more than one
>outstanding request per fd which for PostgreSQL is crappy. There was
>  
>
I had the impression from the kernel aio mailing list a while back that
post-<some kernel version> linux, the POSIX aio calls were forwarded
to the kernel aio interface. Or are you saying that the POSIX API itself 
imposes
that limitation ?