From: Shesha Sreenivasamurthy <shesha@inostor.com>
To: Rob van Nieuwkerk <robn@verdi.et.tudelft.nl>
Cc: linux-kernel@vger.kernel.org, kernelnewbies@nl.linux.org
Subject: Re: O_DIRECT
Date: Wed, 21 Jul 2004 11:45:50 -0700 [thread overview]
Message-ID: <40FEB9DE.5020209@inostor.com> (raw)
In-Reply-To: <20040721201532.7e6161ed.robn@verdi.et.tudelft.nl>
Thank you very much ....
-Shesha
Rob van Nieuwkerk wrote:
>On Wed, 21 Jul 2004 11:01:20 -0700
>Shesha Sreenivasamurthy <shesha@inostor.com> wrote:
>
>Hi Shesha,
>
>
>
>>ohhh OK, if the block size is 4096, then the read/write size must be
>>integer multiple of 4096 ??? is it ???
>>In general should the read/write length be a multiple of block size?
>>
>>
>
>Yes, see my previous emails.
>
> greetings,
> Rob van Nieuwkerk
>
>
>
>>Rob van Nieuwkerk wrote:
>>
>>
>>
>>>On Wed, 21 Jul 2004 10:10:26 -0700
>>>Shesha Sreenivasamurthy <shesha@inostor.com> wrote:
>>>
>>>Hi Shesha,
>>>
>>>You don't mention what the *size* of your read()/write() is.
>>>Besides a requirement on the alignment of the read/write buffer
>>>the size of the read()/write() must also be OK.
>>>
>>> greetings,
>>> Rob van Nieuwkerk
>>>
>>>
>>>
>>>
>>>
>>>>This is what I found ....
>>>>
>>>>Our driver sets the block size to be 4096. so BLKBSZGET will return
>>>>4096. So if I allin the memory at 4096 boundary, I cannot read using
>>>>O_DIRECT. But, if I set the block size to 512. I can read/write
>>>>successfully. It also works with 1024, but no with 4096
>>>>
>>>>So the recepie what I am following is ...
>>>>
>>>>BLKBSZGET -> Get original block size
>>>>BLKBSZSET -> Set the block size to 512
>>>>READ | WRITE Successfully ;)
>>>>BLKBSZSET -> Set back to the original block size
>>>>
>>>>-Shesha
>>>>
>>>>Rob van Nieuwkerk wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>On Tue, 20 Jul 2004 10:27:57 -0700
>>>>>Shesha Sreenivasamurthy <shesha@inostor.com> wrote:
>>>>>
>>>>>Hi Shesha,
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>I am having trouble with O_DIRECT. Trying to read or write from a block
>>>>>>device partition.
>>>>>>
>>>>>>1. Can O_DIRECT be used on a plain block device partition say
>>>>>>"/dev/sda11" without having a filesystem on it.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>yes.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>2. If no file system is created then what should be the softblock size.
>>>>>>I am using the IOCTL "BLKBSZGET". Is this correct?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>yes.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>3. Can we use SEEK_END with O_DIRECT on a partition without filesystem.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>yes.
>>>>>
>>>>>I'm using these exact things in an application.
>>>>>
>>>>>Note that with 2.4 kernels the "granularity" you can use for offset
>>>>>and r/w size is the softblock size (*). For 2.6 the requirements are
>>>>>much more relaxed: it's the device blocksize (typically 512 byte).
>>>>>
>>>>>(*): actually one of offset or r/w size has a smaller minimum if
>>>>>I remember correctly. Don't remember which one. But if you assume
>>>>>the softblock size as a minimum for both you're allways safe.
>>>>>
>>>>> greetings,
>>>>> Rob van Nieuwkerk
>>>>>
>>>>>--
>>>>>Kernelnewbies: Help each other learn about the Linux kernel.
>>>>>Archive: http://mail.nl.linux.org/kernelnewbies/
>>>>>FAQ: http://kernelnewbies.org/faq/
>>>>>
>>>>>
>>>>>.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>--
>>>Kernelnewbies: Help each other learn about the Linux kernel.
>>>Archive: http://mail.nl.linux.org/kernelnewbies/
>>>FAQ: http://kernelnewbies.org/faq/
>>>
>>>
>>>.
>>>
>>>
>>>
>>>
>>>
>
>--
>Kernelnewbies: Help each other learn about the Linux kernel.
>Archive: http://mail.nl.linux.org/kernelnewbies/
>FAQ: http://kernelnewbies.org/faq/
>
>
>.
>
>
>
next prev parent reply other threads:[~2004-07-21 18:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-20 17:27 O_DIRECT Shesha Sreenivasamurthy
2004-07-20 18:48 ` O_DIRECT bert hubert
[not found] ` <40FD6FCB.5020408@inostor.com>
2004-07-20 20:17 ` O_DIRECT bert hubert
2004-07-21 0:10 ` O_DIRECT Rob van Nieuwkerk
2004-07-21 14:45 ` O_DIRECT Devel
[not found] ` <40FE9F3F.2090205@inostor.com>
2004-07-22 9:46 ` O_DIRECT Devel
2004-07-24 9:56 ` O_DIRECT Rogier Wolff
2004-07-26 1:24 ` O_DIRECT Andrew Morton
2004-07-21 0:05 ` O_DIRECT Rob van Nieuwkerk
[not found] ` <40FEA382.8050700@inostor.com>
2004-07-21 17:20 ` O_DIRECT Rob van Nieuwkerk
[not found] ` <40FEAF70.4070407@inostor.com>
2004-07-21 18:15 ` O_DIRECT Rob van Nieuwkerk
2004-07-21 18:45 ` Shesha Sreenivasamurthy [this message]
2004-07-21 23:18 ` O_DIRECT Shesha Sreenivasamurthy
2004-07-21 23:54 ` O_DIRECT Rob van Nieuwkerk
2004-07-22 0:00 ` O_DIRECT Shesha Sreenivasamurthy
2004-07-22 0:18 ` O_DIRECT Rob van Nieuwkerk
2004-07-22 0:48 ` O_DIRECT Shesha Sreenivasamurthy
[not found] <200306262021.h5QKLhN10771@devserv.devel.redhat.com>
[not found] ` <1056706819.2418.11.camel@sisko.scot.redhat.com>
2003-06-27 10:35 ` O_DIRECT Stephen C. Tweedie
2003-06-27 11:07 ` O_DIRECT Alan Cox
[not found] <200208291113.g7TBDut26852@tench.street-vision.com>
2002-08-29 11:22 ` O_DIRECT Peter T. Breuer
2002-08-29 12:14 ` O_DIRECT Peter T. Breuer
-- strict thread matches above, loose matches on Subject: below --
2002-08-29 11:04 O_DIRECT Peter T. Breuer
2001-04-12 21:09 O_DIRECT Andrea Arcangeli
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=40FEB9DE.5020209@inostor.com \
--to=shesha@inostor.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robn@verdi.et.tudelft.nl \
/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