Date: Fri, 21 Nov 2003 11:45:13 -0800
From: Andrew Morton <akpm@osdl.org>
To: <dhruv.anand@wipro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DIRECT IO for ext3/ext2.
Message-Id: <20031121114513.6bb2e795.akpm@osdl.org>
In-Reply-To: <1E27FF611EBEFB4580387FCB5BEF00F3013DEF08@blr-ec-msg04.wipro.com>
References: <1E27FF611EBEFB4580387FCB5BEF00F3013DEF08@blr-ec-msg04.wipro.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 867
Lines: 27

<dhruv.anand@wipro.com> wrote:
>
> Thanks for your reply. I looked into the boundary alignment issue. 
>  Observed something strange happening;
> 
>  I wrote my own kernel module and then;
>  1. retrieved the block size = 4096 using block_size(struct block_device
>  *bdev) 
>  2. in the user application i did a lseek by 4906 (block size seek) 
>  3. then found the address of the variable i wanted to read into, to be
>  block 
>     size aligned.

O_DIRECT works - trust me ;)

Please grab

	http://www.zip.com.au/~akpm/linux/patches/stuff/ext3-tools.tar.gz

There are a number of examples in there (odread.c is one).


-
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/