From: Xiaoli Feng <xifeng@redhat.com>
To: CIFS <linux-cifs@vger.kernel.org>
Subject: Memory alignment requirement for Direct/IO
Date: Tue, 30 Apr 2019 05:01:06 -0400 (EDT) [thread overview]
Message-ID: <151404631.6398428.1556614866154.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1666985748.6396792.1556614132673.JavaMail.zimbra@redhat.com>
Hello,
I setup samba server in upstream and mount it in local with cache=none,vers=3.11. Then test
the Direct/IO function like this:
fd=open(fname, O_DIRECT | O_RDWR | O_CREAT, 0666))
lseek(fd, 0, SEEK_SET);
read(fd, buf, 1);
For local filesystem such as XFS, "read" will be failed because XFS has 512Byte memory aligment
for Direct/IO. But it's success for cifs. I don't know if it's expected. Could anybody tell me
more about Direct/IO for cifs?
Thanks.
--
Best regards!
XiaoLi Feng 冯小丽
Red Hat Software (Beijing) Co.,Ltd
filesystem-qe Team
IRC:xifeng,#channel: fs-qe
Tel:+86-10-8388112
9/F, Raycom
next parent reply other threads:[~2019-04-30 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1666985748.6396792.1556614132673.JavaMail.zimbra@redhat.com>
2019-04-30 9:01 ` Xiaoli Feng [this message]
2019-05-01 15:35 ` Memory alignment requirement for Direct/IO Steve French
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=151404631.6398428.1556614866154.JavaMail.zimbra@redhat.com \
--to=xifeng@redhat.com \
--cc=linux-cifs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).