> I'm somewhat confused by the complexity. Currently we can already have aNope, fuse never had dirty pages. It does normal writes synchronously, just updating the cache. The dirty accounting and then the per-bdi throttling basically made it possible _at_all_ to have a chance at a writepage implementation which is not deadlocky (so thanks for those ;). But there's still the throttle_vm_writeout() thing, and the other places where the kernel is waiting for a write to complete, which just cannot be done within a constrained time if an unprivileged userspace process is involved. Miklos - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| David Woodhouse | [GIT *] Allow request_firmware() to be satisfied from in-kernel, use it in more dr... |
| Philipp Marek | Re: sys_chroot+sys_fchdir Fix |
| Greg Kroah-Hartman | [PATCH 008/196] Chinese: add translation of volatile-considered-harmful.txt |
git: | |
| Krishna Kumar | [PATCH 9/10 REV5] [IPoIB] Implement batching |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
