All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fernando Dammous" <ferdam@internetcom.com.br>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Linux LVM msede <linux-lvm@msede.com>
Subject: Re: [linux-lvm] LVM, raw-io, devfs
Date: Sat, 2 Oct 1999 14:08:09 -0300	[thread overview]
Message-ID: <002e01bf0cf8$b4667720$030116ac@fd1> (raw)
In-Reply-To: 14324.58266.920834.895229@dukat.scot.redhat.com

HI Stephen and everybody,

> I've never tried the raw IO code on 2.0: let me know how it goes!  In
> principle, there is no reason why raw IO on LVM should not work.
>
> --Stephen
>

I prefer to update my kernel (to 2.3.18 or even to wait for the 2.4), before
and then to use RAW-IO.
I just hope I can simply alter Oracle to use RAW-IO instead of having
reinstall it.
Using Oracle with LVM is already very good, with RAW-IO it will be better (I
believe).
In any way, I thank in advance for your interest (and of all people of here)
in helping me in this case.

Thank you very much

Fernando

  parent reply	other threads:[~1999-10-02 17:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-01  2:48 [linux-lvm] LVM, raw-io, devfs Fernando Dammous
1999-10-01 12:40 ` Adrien Farkas
1999-10-01 16:38 ` Stephen C. Tweedie
1999-10-01 18:39   ` Drew Smith
1999-10-01 19:15     ` Luca Berra
1999-10-02 15:01     ` Stephen C. Tweedie
1999-10-02 15:53       ` Eric Smith
1999-10-03  7:43     ` Harald Milz
1999-10-02 17:08   ` Fernando Dammous [this message]
1999-10-03  5:56     ` pamvdam
1999-10-04 10:43       ` Stephen C. Tweedie
1999-10-04 11:03         ` pamvdam
1999-10-03 10:14     ` Adrien Farkas
1999-10-03 17:23       ` Fernando Dammous
1999-10-04  9:28         ` Adrien Farkas
1999-10-04 10:44       ` Stephen C. Tweedie
  -- strict thread matches above, loose matches on Subject: below --
1999-10-03 13:06 Daniel Whicker

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='002e01bf0cf8$b4667720$030116ac@fd1' \
    --to=ferdam@internetcom.com.br \
    --cc=linux-lvm@msede.com \
    --cc=sct@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.