From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Peter Schiffer <pschiffe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
esandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [patch] open.2: Update note about the alignment of the user buffer and the file offset for O_DIRECT flag
Date: Tue, 22 Apr 2014 20:04:14 +0200 [thread overview]
Message-ID: <5356AF1E.7020906@gmail.com> (raw)
In-Reply-To: <5356A50F.4010602-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On 04/22/2014 07:21 PM, Peter Schiffer wrote:
> Hello Michael,
>
> the sentence in open(2) man page in notes for O_DIRECT flag:
> "Under Linux 2.6, alignment to 512-byte boundaries suffices."
>
> is not universally correct. The alignment is a property of the storage,
> for example, 4k-sector drives with no 512 byte sector emulation will be
> unable to perform 512-byte direct I/O.
>
> The patch clarifies this sentence.
Thanks very much for that patch, Peter. It clears
up my (mis)understanding! Applied.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-04-22 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 17:21 [patch] open.2: Update note about the alignment of the user buffer and the file offset for O_DIRECT flag Peter Schiffer
[not found] ` <5356A50F.4010602-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-04-22 18:04 ` Michael Kerrisk (man-pages) [this message]
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=5356AF1E.7020906@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=esandeen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pschiffe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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).