public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Susæg" <Michael.Susag@fast.no>
To: linux-kernel@vger.kernel.org
Subject: O_DIRECT support in 2.4.4?
Date: Fri, 27 Apr 2001 18:08:41 +0200	[thread overview]
Message-ID: <3AE99989.EF69C2D5@fast.no> (raw)

[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]

We have tested the rawio and o_direct patches from Andrea Arcangeli 
with great success, and wondered if they will be part of the next 
kernel release, 2.4.4?

So far we have tested these patches on four different systems.
With the latest versions of these patches (rawio-6, o_direct-3) 
all systems works perfectly ok. Both with and without O_DIRECT 
enabled in big file operations.

The O_DIRECT support really helps performance a lot
for some types of applications. We happen to have such an 
application, and we would like to see O_DIRECT 
support in the kernel source in the near future.
 
This would lift Linux to a new level in terms of disk performance
for "self-caching" applications.

A performance test we did on our application shows a huge 
improvement, upto 8 times better data read speed with direct-IO.
With buffered IO, the CPU is doing caching most of the time.

I attached a graph showing this performance win using O_DIRECT
versus buffered IO. Each thread reads at a random offset a random 
amount of data from a big data set. The dataset is placed on 
a software RAID 0 with many disks. With that configuration 
we are able to fully utilize the 160 MB/s SCSI controllers.



-- 
Michael Susæg, M.Eng.             Mail:  Michael.Susag@fast.no
Software Engineer                 Web:   http://www.fast.no/
Fast Search & Transfer ASA        Phone: +47 21 60 12 27
P.O. Box 1677 Vika                Fax:   +47 21 60 12 01
NO-0120 Oslo, NORWAY

Try FAST Search: http://www.alltheweb.com/

[-- Attachment #2: directio.png --]
[-- Type: image/png, Size: 4983 bytes --]

                 reply	other threads:[~2001-04-27 16:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3AE99989.EF69C2D5@fast.no \
    --to=michael.susag@fast.no \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox