All of lore.kernel.org
 help / color / mirror / Atom feed
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 10:10:33 +0400	[thread overview]
Message-ID: <434B5759.1090604@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0510101734440.3955@dacun.noviforum.si>

[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]

Hello

Gorazd Golob wrote:
> 
> It doesn't work right - your example :(
> 
> Our programmers said that ssize_t type should be used instead of size_t
> for rd variable..
> 

ok, yes, I agree. But it should not change anything.
Please try new version. It works fine here. How does it behave on your side?

> in code is:
> 
> size_t rd;
> 
> 
> tnx, gorazd
> 
> 
> On Mon, 10 Oct 2005, Vladimir V. Saveliev wrote:
> 
>> Hello
>>
>> Gorazd Golob wrote:
>>>
>>>
>>> On Mon, 10 Oct 2005, Vladimir V. Saveliev wrote:
>>>
>>>>
>>>> Does it work on ext2?
>>> Yes it work on ext2, ext3, xfs ..
>>>
>>>> Are you sure that file offset is properly aligned?
>>> Yes ..
>>>
>> Would you please try whether the attached program works for you?
>>
>>>
>>>>
>>>>> Without O_DIRECT works fine as said in previous mails. Write with
>>>>> O_DIRECT works fine. Kernel version is:
>>>>> Linux xxxx 2.6.12.6 #6 SMP Thu Sep 15 12:29:53 CEST 2005 x86_64
>>>>> Intel(R)
>>>>> Xeon(TM) CPU 3.00GHz GenuineIntel GNU/Linux
>>>>>
>>>>> please let me know if you need more info.
>>>>>
>>>>> tnx, Gorazd
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>> Or in other words is reiserfs3 supporting reading with O_DIRECT
>>>>>>> flag?
>>>>>>> Writing works well with 0_DIRECT on reiserfs3.
>>>>>>>
>>>>>>> Gorazd
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
> 
> 


[-- Attachment #2: test-direct-io.c --]
[-- Type: text/x-c, Size: 668 bytes --]

#define _XOPEN_SOURCE 600
#include <stdio.h>
#include <unistd.h>
#include <malloc.h>
#include <stdlib.h>
#include <fcntl.h>

#define O_DIRECT   040000

int main(int argc, char **argv)
{
	int fd;
	ssize_t rd;
	char *buf;

	if (argc != 2) {
		printf("%s filename\n", argv[0]);
		return 0;
	}
	fd = open(argv[1], O_RDONLY | O_DIRECT);
	if (fd == -1) {
		perror("open failed");
		return 0;
	}
	if (posix_memalign((void **)&buf, 4096, 4096)) {
		perror("malloc failed");
                return 0;
	}
	rd = read(fd, buf, 4096);
	if (rd != 4096) {
                perror("read failed");
                return 0;
	}
	printf("read ok\n");
	free(buf);
	close(fd);
	return 0;
}

  reply	other threads:[~2005-10-11  6:10 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 [this message]
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
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=434B5759.1090604@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.