From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Gorazd Golob <gorazdg@noviforum.si>
Cc: reiserfs-list@namesys.com
Subject: Re: reiser3 and O_DIRECT read
Date: Tue, 11 Oct 2005 16:06:04 +0400 [thread overview]
Message-ID: <434BAAAC.2030403@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0510110955320.3955@dacun.noviforum.si>
Hello
Gorazd Golob wrote:
>
> Vladimir,
>
> I forgot to tell that we're using x86_64.
ok
> Kernel is:
> Linux xxxx 2.6.12.6 #6 SMP Thu Sep 15 12:29:53 CEST 2005 x86_64 Intel(R)
Did you find parameters with which the program behaves differently for a file on
ext2 and reiserfs?
> Xeon(TM) CPU 3.00GHz GenuineIntel GNU/Linux
>
> On Tue, 11 Oct 2005, Vladimir V. Saveliev wrote:
>
>> Hello
>>
>> Gorazd Golob wrote:
>>>
>>> ;(
>>>
>>> works ok if file is bigger than about 4000 bytes. Otherwise read failed.
>>>
>> Yes, using O_DIRECT you should care about alignment to boundary of 512
>> bytes for
>> address of buffer you read to, size of that buffer and offset in a
>> file to read
>> from.
>>
>> Please try this version of test program and let us know how to make it
>> to behave
>> differently for file in reiserfs and ext2.
>> What is version of kernel you use?
>>
>
>
next prev parent reply other threads:[~2005-10-11 12:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 10:13 reiser3 and O_DIRECT read Gorazd Golob
2005-10-07 13:29 ` Vladimir V. Saveliev
2005-10-10 10:41 ` Gorazd Golob
2005-10-10 12:22 ` Vladimir V. Saveliev
2005-10-10 12:30 ` Gorazd Golob
2005-10-10 13:08 ` Vladimir V. Saveliev
2005-10-10 13:22 ` Gorazd Golob
2005-10-10 15:40 ` Gorazd Golob
2005-10-11 6:10 ` Vladimir V. Saveliev
2005-10-11 6:36 ` Gorazd Golob
2005-10-11 7:30 ` Vladimir V. Saveliev
2005-10-11 7:56 ` Gorazd Golob
2005-10-11 12:06 ` Vladimir V. Saveliev [this message]
2005-10-11 16:07 ` Hans Reiser
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=434BAAAC.2030403@namesys.com \
--to=vs@namesys.com \
--cc=gorazdg@noviforum.si \
--cc=reiserfs-list@namesys.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.