posix_fallocate(2)
mdf at FreeBSD.org
mdf at FreeBSD.org
Thu Apr 14 19:35:38 UTC 2011
For work we need a functionality in our filesystem that is pretty much
like posix_fallocate(2), so we're using the name and I've added a
default VOP_ALLOCATE definition that does the right, but dumb, thing.
The most recent mention of this function in FreeBSD was another thread
lamenting it's failure to exist:
http://lists.freebsd.org/pipermail/freebsd-ports/2010-February/059268.html
The attached files are the core of the kernel implementation of the
syscall and a default VOP for any filesystem not supporting
VOP_ALLOCATE, which allows the syscall to work as expected but in a
non-performant manner. I didn't see this syscall in NetBSD or
OpenBSD, so I plan to add it to the end of our syscall table.
What I wanted to check with -arch about was:
1) is there still a desire for this syscall?
2) is this naive implementation useful enough to serve as a default
for all filesystems until someone with more knowledge fills them in?
3) are there any obvious bugs or missing elements?
Thanks,
matthew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: posix_fallocate.2
Type: application/octet-stream
Size: 4070 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-arch/attachments/20110414/39b033e4/posix_fallocate.obj
More information about the freebsd-arch
mailing list