> 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
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 006/196] Chinese: add translation of oops-tracing.txt |
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
| David Miller | Re: [PATCH] Stop pmac_zilog from abusing 8250's device numbers. |
git: | |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Linus Torvalds | Re: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49 |
