From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Cc: ross.zwisler@linux.intel.com, jack@suse.cz
Subject: [PATCH 0/3] xfsprogs: FS_IOC_FS[SG]ETXATTR and DAX support
Date: Mon, 15 Feb 2016 16:32:23 +1100 [thread overview]
Message-ID: <1455514346-15481-1-git-send-email-david@fromorbit.com> (raw)
Hi folks,
There are two parts to this patchset. The first is ensuring that
xfsprogs builds correctly with the new kernel header provided
definitions of XFS_IOC_FS[SG]SETXATTR and it's flags. I modified
my original approach to this to hide the definitions of the FS*
ioctl and flags in the platofrm headers if the system didn't provide
them.
While this does result in some duplication, it solves the problem of
needing different definitions for FS_IOC_FS[SG]ETXATTR on different
platforms - they are different ioctl names on IRIX, so we can't just
define it once in xfs_fs.h. The detection can also then be different
- we only include the definitions on linux if we don't have the
system version, and on the other platforms it retains the
HAVE_FSXATTR guards.
The second and third patches are adding support for the FS_XFLAG_DAX
and enabling xfs_io to set, get and clear the flag. Actual support
of the on disk flag in libxfs will come in a later patchset that
adds support into db and repair, too. This is the patchset I used to
test the kernel side flag support.
Comments and testing welcome.
Cheers,
Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2016-02-15 5:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 5:32 Dave Chinner [this message]
2016-02-15 5:32 ` [PATCH 1/3] xfs_fs.h: XFS_IOC_FS[SG]SETXATTR to FS_IOC_FS[SG]ETXATTR promotion Dave Chinner
2016-02-15 23:43 ` Eric Sandeen
2016-02-15 5:32 ` [PATCH 2/3] xfs: introduce per-inode DAX enablement Dave Chinner
2016-02-15 23:44 ` Eric Sandeen
2016-02-15 5:32 ` [PATCH 3/3] xfs_io: add support for changing the new inode DAX attribute Dave Chinner
2016-02-15 23:46 ` Eric Sandeen
2016-02-17 22:53 ` Ross Zwisler
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=1455514346-15481-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=ross.zwisler@linux.intel.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