public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@timpanogas.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: dalecki@evision-ventures.com, linux-kernel@vger.kernel.org
Subject: Re: ORACLE and 2.4-test10
Date: Fri, 17 Nov 2000 12:10:36 -0700	[thread overview]
Message-ID: <3A1582AC.1778C336@timpanogas.org> (raw)
In-Reply-To: <E13wqb5-00012V-00@the-village.bc.nu>



Alan Cox wrote:
> 
> > performance, so we came up with something called direct FS, a separate
> > File System interface just for Oracle.  The SOSD layer inside of Oracle
> 
> Yeah but you see thats ugly
> 
> > In NetWare, directFS was little more than a "raw" interface that
> > bypassed the file cache.  It would be like having an API to a direct
> > physical file system that never cached data in the buffer cache.  In
> 
> Its called O_DIRECT and kiovecs. Its already there. Much more generic than
> an 'oraclefs'

Then they should have what they need.  If they have an SOSD plugin, no
reason 
it shouldn't run.

8)

Jeff

> 
> Alan
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-17 19:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-17 18:50 ORACLE and 2.4-test10 dalecki
2000-11-17 17:53 ` Christoph Rohland
2000-11-17 18:14 ` Alan Cox
2000-11-17 18:30   ` Jeff V. Merkey
2000-11-17 18:50     ` Alan Cox
2000-11-17 19:10       ` Jeff V. Merkey [this message]
2000-11-18 11:07   ` Frank van Maarseveen
2000-11-18 17:22     ` Alan Cox
2000-11-18 17:28     ` Josue Emmanuel Amaro

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=3A1582AC.1778C336@timpanogas.org \
    --to=jmerkey@timpanogas.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dalecki@evision-ventures.com \
    --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