From: Eric Sandeen <sandeen@redhat.com>
To: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH 0/3 V3] xfs: allow logical-sector sized O_DIRECT for any fs sector size
Date: Tue, 21 Jan 2014 16:43:41 -0600 [thread overview]
Message-ID: <52DEF81D.4090100@redhat.com> (raw)
Ok once more with feeling.
Patchset to allow sub-fs-metadata-sector-sized DIOs.
I have (still) explicitly not changed XFS_IOC_DIOINFO output for now;
it still reports the actual minimum sizes and alignments which will
be allowed by the filesystem (and block layer beneath it).
Thanks,
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-01-21 22:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 22:43 Eric Sandeen [this message]
2014-01-21 22:44 ` [PATCH 1/3 V3] xfs: clean up xfs_buftarg Eric Sandeen
2014-01-22 23:12 ` Dave Chinner
2014-01-21 22:45 ` [PATCH 2/3 V3] xfs: rename xfs_buftarg structure members Eric Sandeen
2014-01-22 23:13 ` Dave Chinner
2014-01-21 22:46 ` [PATCH 3/3 V3] xfs: allow logical-sector sized O_DIRECT Eric Sandeen
2014-01-22 13:54 ` Brian Foster
2014-01-22 23:14 ` Dave Chinner
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=52DEF81D.4090100@redhat.com \
--to=sandeen@redhat.com \
--cc=xfs@oss.sgi.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 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).