* raw I/O support for Fedora Core 4
@ 2006-03-23 9:24 Yogesh Pahilwan
2006-03-23 10:07 ` Arjan van de Ven
2006-03-23 15:47 ` Phillip Susi
0 siblings, 2 replies; 3+ messages in thread
From: Yogesh Pahilwan @ 2006-03-23 9:24 UTC (permalink / raw)
To: linux-kernel; +Cc: linux-raid
Hi All,
I want to do raw I/O on MD RAID and LVM for fedora core 4(kernel 2.6.15.6).
After doing googling I came to know that "raw" command does the raw
operation by linking
MD device and LVM volume to the raw device as
# raw /dev/raw/raw1 /dev/md0.
But when I search on this I came to know that there is no raw (/dev/rawctl)
device support available with 2.6 kernel.
I have also tried recompile the kernel sources with raw device support it is
not getting compiled as it is obsolete in 2.6.
If I want to include raw device support in my kernel what should I will have
to do, so that I
Will be able to do raw I/O on MD device and LVM volumes.
Thanks and Regards,
Yogesh
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: raw I/O support for Fedora Core 4
2006-03-23 9:24 raw I/O support for Fedora Core 4 Yogesh Pahilwan
@ 2006-03-23 10:07 ` Arjan van de Ven
2006-03-23 15:47 ` Phillip Susi
1 sibling, 0 replies; 3+ messages in thread
From: Arjan van de Ven @ 2006-03-23 10:07 UTC (permalink / raw)
To: Yogesh Pahilwan; +Cc: linux-kernel, linux-raid
On Thu, 2006-03-23 at 14:54 +0530, Yogesh Pahilwan wrote:
> Hi All,
>
> I want to do raw I/O on MD RAID and LVM for fedora core 4(kernel 2.6.15.6).
>
> After doing googling I came to know that "raw" command does the raw
> operation by linking
> MD device and LVM volume to the raw device as
>
> # raw /dev/raw/raw1 /dev/md0.
>
> But when I search on this I came to know that there is no raw (/dev/rawctl)
> device support available with 2.6 kernel.
> I have also tried recompile the kernel sources with raw device support it is
> not getting compiled as it is obsolete in 2.6.
> If I want to include raw device support in my kernel what should I will have
> to do, so that I
the preferred interface is doing O_DIRECT io on the device node itself,
rather than going via a (slower) indirection layer such as "raw". ("raw"
is just a wrapper on top of O_DIRECT basically in 2.6 kernels so slower)
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: raw I/O support for Fedora Core 4
2006-03-23 9:24 raw I/O support for Fedora Core 4 Yogesh Pahilwan
2006-03-23 10:07 ` Arjan van de Ven
@ 2006-03-23 15:47 ` Phillip Susi
1 sibling, 0 replies; 3+ messages in thread
From: Phillip Susi @ 2006-03-23 15:47 UTC (permalink / raw)
To: Yogesh Pahilwan; +Cc: linux-kernel, linux-raid
The raw device driver is obsolete because it has been superseded by the
O_DIRECT open flag. If you want to have dd perform unbuffered IO then
pass the iflag=direct option for input, or oflag=direct option for
output, and it will use O_DIRECT to bypass the buffer cache.
This of course assumes that you mean "bypass the buffer cache" when you
say "raw io".
Yogesh Pahilwan wrote:
> Hi All,
>
> I want to do raw I/O on MD RAID and LVM for fedora core 4(kernel 2.6.15.6).
>
> After doing googling I came to know that "raw" command does the raw
> operation by linking
> MD device and LVM volume to the raw device as
>
> # raw /dev/raw/raw1 /dev/md0.
>
> But when I search on this I came to know that there is no raw (/dev/rawctl)
> device support available with 2.6 kernel.
> I have also tried recompile the kernel sources with raw device support it is
> not getting compiled as it is obsolete in 2.6.
> If I want to include raw device support in my kernel what should I will have
> to do, so that I
> Will be able to do raw I/O on MD device and LVM volumes.
>
> Thanks and Regards,
> Yogesh
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-03-23 15:47 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-03-23 9:24 raw I/O support for Fedora Core 4 Yogesh Pahilwan
2006-03-23 10:07 ` Arjan van de Ven
2006-03-23 15:47 ` Phillip Susi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).