On Wed, 2003-02-12 at 17:03, Andrew Morton wrote:
> Bruno Diniz de Paula <diniz@cs.rutgers.edu> wrote:
> >
> > Hi,
> >
> > I am trying to use O_DIRECT to read ordinary files and read syscall
> > always returns 0, unless when the file size equals the fs block size.
>
> It should be returning -1, with errno set to EINVAL.
But I am using multiples of page size in both buffer alignment and
buffer size (2nd and 3rd parameters of read). The issue is that when I
try to read files with sizes that are NOT multiples of block size (and
therefore also not multiples of page size), the read syscall returns 0,
with no errors. With files of size 4096, 8192 etc, everything works
fine. The errors shouldn't occur indeed, as I am using the correct
alignment and size to read. So the question remains, am I able to read
just files whose size is a multiple of block size?
Thanks,
Bruno.
PS: I am running 2.4.20...
>
> > Is
> > it true that I can only use O_DIRECT when the size of the file written
> > in the inode is a multiple of block size?
> >
>
> The file can be of any size - the kernel will zero-fill any remaining bytes.
>
> The address and length which you pass into the read() or write() system call
> must both be a multiple of the filesystem block size.
>
> It is always safe to just use the machine's page size for alignment
> calculations - no filesystem has a blocksize larger than the pagesize.
>
> A good way to do this is to run getpagesize(), and to then malloc a buffer
> which is one page larger than you need. Then round that address up to the
> next page boundary. And perform I/O into that memory with
> multiple-of-page-size requests.
>
>
>
> In the 2.5 kernel the "must be a multiple of blocksize" requirement was
> relaxed. We now support alignments and lengths down to the minimum which is
> supported by the underlying device. Typically 512 bytes, but not always.
>
> Portable applications should not assume that 512-byte alignment is supported.
> They should query the device's aligment requirements via the BLKSSZGET ioctl
> against (say) /dev/hda1. Or they can simply try 512, 1024, 2048, ... at
> initialisation time.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
-- Bruno Diniz de Paula <diniz@cs.rutgers.edu> Rutgers University
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Feb 15 2003 - 22:00:45 EST