From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 11 May 2002 10:25:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 11 May 2002 10:25:38 -0400 Received: from ns.virtualhost.dk ([195.184.98.160]:60132 "EHLO virtualhost.dk") by vger.kernel.org with ESMTP id ; Sat, 11 May 2002 10:25:37 -0400 Date: Sat, 11 May 2002 16:24:34 +0200 From: Jens Axboe To: Roy Sigurd Karlsbakk Cc: Linus Torvalds , Lincoln Dale , Andrew Morton , Alan Cox , Martin Dalecki , Padraig Brady , Anton Altaparmakov , Kernel Mailing List Subject: Re: O_DIRECT performance impact on 2.4.18 (was: Re: [PATCH] 2.5.14 IDE 56) Message-ID: <20020511142434.GA1224@suse.de> In-Reply-To: <200205111418.g4BEIa629620@mail.pronto.tv> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i X-OS: Linux 2.4.19-pre8 i686 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sat, May 11 2002, Roy Sigurd Karlsbakk wrote: > On Friday 10 May 2002 17:55, Linus Torvalds wrote: > > On Fri, 10 May 2002, Lincoln Dale wrote: > > > so O_DIRECT in 2.4.18 still shows up as a 55% performance hit versus no > > > O_DIRECT. anyone have any clues? > > > > Yes. > > > > O_DIRECT isn't doing any read-ahead. > > > > For O_DIRECT to be a win, you need to make it asynchronous. > > Will the use of O_DIRECT affect disk elevatoring? No, the I/O scheduler can't even tell whether it's being handed O_DIRECT buffers or not. Jens