Linux has a couple of "interesting" ioctls which in one case would allow faster + Sparse-accurate file handling in one go.
FIEMAP Recommended LWN article: SEEK_HOLE or FIEMAP? http://lwn.net/Articles/260795/ When an application wants to know how a file is store in the disk (for example, a backup application that wants to know if a file is a sparse file and wants to avoid backing up the hole) it uses the fibmap ioctl. But this ioctl is suboptimal - the ioctl can only be asked for a block at a time, which is too expensive for big files. The FIEMAP ioctl, in the other hand, returns a list of extents. (It's aimed at handling sparse files without the overheads.) Other OSes also have this ioctl, or an equivalent version. Is anyone interested/able to code for it? ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
