View Single Post
Old 11-04-2012, 10:08 PM   #38
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by geekmaster View Post
Perhaps loop mounting a raw partition would be faster and use less RAM when NOT going through layers of loop mounting an image file on a fuse filesystem, and the vfat support and all that...
This last paragraph is the key to the behavior -
the number of VFS layers involved.

Using the loop driver to provide a device-to-device layer (although called part of the Virtual File System) is just a device offset calculation operating below the file-to-device layers.

Plus, adding in a user space file system layer - most bets are off.
The kernel can control, and usually recover from, what happens in kernel space (things like potential deadlock paths).
It has no control over what user space does until it makes a call into kernel space.
knc1 is offline   Reply With Quote