Re: FALLOC_FL_COLLAPSE_RANGE?

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

 



On 08/22/2014 06:27 AM, Justin Clift wrote:
Just noticed this:

   http://article.gmane.org/gmane.comp.file-systems.xfs.general/60475

Is it something of interest to us?

I have been meaning to explore adding both FALLOC_FL_COLLAPSE_RANGE and FALLOC_FL_ZERO_RANGE flags to fallocate() in glusterfs but never got around to it. Don't know if the feature is beneficial per se (see comments in http://lwn.net/Articles/589260/ ), but since it has been merged in the 3.15 kernel, I guess it's going to be around forever. Let me take this up. Apparently more flags (FALLOC_FL_INSERT_RANGE and IOC_MOV_DATA) are in the works for fallocate().

Ravi


+ Justin

--
GlusterFS - http://www.gluster.org

An open source, distributed file system scaling to several
petabytes, and handling thousands of clients.

My personal twitter: twitter.com/realjustinclift

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux