Re: [fuse-devel] Optimizing unlink in the high-level API

[David S. <da...@da...>]

On Mon, Feb 18, 2013 at 8:22 PM, Nikolaus Rath <Nik...@ra...> wrote:
> That doesn't make sense. The high level API is implemented on top of the
> low level API, so it cannot possibly be faster. It could be the case
> that NTFS3g isn't as clever as the FUSE library that implements the high
> level API when using the low level API, but that's something that would
> be specific to NTFS3g and probably not too hard to fix either.

Totally possible. I didn't investigate their claim [1] further, but here it is:

"The high level interface performs generally better because several
system calls are grouped to form a single file system call [which] can
generally be processed in the file system with a couple of inode
openings (for the requested file and parent directory), whereas at low
level more file system calls are needed causing reopenings of inodes."

I had initially read it to mean that the calls happened at a higher
level from the kernel and resulted in fewer user-space requests. I now
understand that that's not the case.

[1] http://b.andre.pagesperso-orange.fr/fuse-interfaces.html

--
David Strauss
   | da...@da...
   | +1 512 577 5827 [mobile]