From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id 14CCFBC37 for ; Thu, 29 Oct 2009 21:59:07 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhICAD+e6UrU4367kGdsb2JhbACBT5l5AQEBAQkJDAcTA8NqAoQ7BA X-IronPort-AV: E=Sophos;i="4.44,648,1249250400"; d="scan'208";a="49485906" Received: from moutng.kundenserver.de ([212.227.126.187]) by mail4-smtp-sop.national.inria.fr with ESMTP; 29 Oct 2009 21:59:06 +0100 Received: from office1.lan.sumadev.de (dslb-094-219-209-052.pools.arcor-ip.net [94.219.209.52]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0MbLNo-1MnBh5319g-00JBel; Thu, 29 Oct 2009 21:59:03 +0100 Received: from [192.168.5.104] (dslb-094-219-209-052.pools.arcor-ip.net [94.219.209.52]) by office1.lan.sumadev.de (Postfix) with ESMTPSA id 32F95C0E8E; Thu, 29 Oct 2009 21:59:03 +0100 (CET) Subject: Re: [Caml-list] Re: How to read different ints from a Bigarray? From: Gerd Stolpmann To: Florian Weimer Cc: Goswin von Brederlow , caml-list@inria.fr In-Reply-To: <87639yue6y.fsf@mid.deneb.enyo.de> References: <87eiond3of.fsf@frosties.localdomain> <87639zd0m9.fsf@frosties.localdomain> <87639yue6y.fsf@mid.deneb.enyo.de> Content-Type: text/plain Date: Thu, 29 Oct 2009 22:04:04 +0100 Message-Id: <1256850244.24202.105.camel@flake.lan.gerd-stolpmann.de> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX18B+jBHfsBXfjcSNgyRs4fvvxogE9+w+Bv2Djp 01LEzDUvuKGpCK3C//hemshzolPkwQ/zO5cYl/SfmwN2Z5/6lh FYNAe04r2gMcYsicfKtFw== X-Spam: no; 0.00; bigarray:01 gerd:01 stolpmann:01 gerd:01 donnerstag:01 aligned:01 afaik:01 stolpmann:01 darmstadt:01 6151:01 6151:01 ints:01 caml-list:01 data:02 rarely:02 Am Donnerstag, den 29.10.2009, 21:40 +0100 schrieb Florian Weimer: > * Goswin von Brederlow: > > > - The data is passed to libaio and needs to be kept alive and unmoved > > as long as libaio knows it. > > It also has to be aligned to a 512-byte boundary, so you can use > O_DIRECT. Linux does not support truely asynchronous I/O without > O_DIRECT AFAIK, which rarely makes it worth the trouble. Right. There is also the question whether aio for regular files (i.e. files backed by page cache) is continued to be supported at all - it is well known that Linus Torvalds doesn't like it. It can happen that at some day aio will be restricted to block devices only. So I wouldn't use it for production code, but it is of course still an interesting interface. Gerd -- ------------------------------------------------------------ Gerd Stolpmann, Bad Nauheimer Str.3, 64289 Darmstadt,Germany gerd@gerd-stolpmann.de http://www.gerd-stolpmann.de Phone: +49-6151-153855 Fax: +49-6151-997714 ------------------------------------------------------------