Nikolay Pertsev: > I thought it is better because you wrote: "I hope this patch will be more > effective than aufs "trunc_xino" option."
Here I meant "how good to your problem" by the word "effective". Note that your problem is about space instead of time. - "trunc_xino" reduces the number of consumed blocks by XINO files. But it is not guranteed, and sometimes the number will be little. - "ino" option for tmpfs ensures the lowest unused inum, and it makes aufs XINO files always smallest. So the latter is "effective" to the "space" problem. And I am still considering these two points. - generality of the patch Because the patch is not for aufs, it can widely affect your system. Of course, "noino" is for that case. - performance of the patch Because it depends upon a single lock, it can be a bottle-neck somtimes I am afraid. J. R. Okajima ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce
