Re: [PATCH 0/4] Fiemap, an extent mapping ioctl - round 2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Assuming I am correct in at least part of my understanding
on why there is

> * FIEMAP_FLAG_SYNC
> If this flag is set, the kernel will sync the file before mapping extents.

I propose we replace it with the following flag that should
provide everything XFS needs:

* FIEMAP_FLAG_ANY
* Advisory only - If this flag is set, the filesystem can
* ignore normal consistency checks when returning data.

Then with the flag==0, XFS does the locked-atomic-sync and
with the flag==1, XFS works like other filesystems that
don't do the atomic stuff.

jim
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux