Greg Freemyer wrote:
Greg Freemyer wrote:
To repeat:
with dd -> ext4 75 MB/sec data transfer and 160% cpu load (uses multiple cores. No single core overloaded.)
with dd -> ntfs 25-30 MB/sec data transfer and only 120% cpu load (one core running mount.ntfs at 75% load)
I actually find that kind of strange, but it was repeatable.
I think it is pretty clear that mount.ntfs is the bottleneck.
I guess mount.ntfs is the FUSE binary?
I don't think fuse has a binary. It is in the kernel and provides a kernel api. There is a fuse library that binaries can use.
fuse does have a binary, that is the user space part. (I wrote a fuse myself a couple of years ago). The user-space binary is basically the code for the various filesystem operations: getattr, readdir, opendir, releasedir, open, release, read etc.
With fuse, the logic is pushed to userspace. I believe that mount.ntfs is the program that implements the logic required to read/write a ntfs filesystem. It uses the fuse api, but I would not call it the fuse binary.
Okay, I would call that the binary, but it doesn't matter. -- Per Jessen, Zürich (3.4°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org