> The next point then, I'd expect your fuse_page_mkwrite() to pushYou're talking about this: + wait_event(fc->writeback_waitq, + fc->numwrite < FUSE_WRITEBACK_THRESHOLD); right? It's one of the things I need to clean out, there's no point in fc->numwrite, which is essentially the same as the BDI_WRITEBACK counter. OTOH, I'm thinking about adding a per-fs limit (adjustable for privileged mounts) of dirty+writeback. I'm not sure how hard would it be to add support for this into balance_dirty_pages(). So I'm thinking of a parameter in struct backing_dev_info that is used to clip the calculated per-bdi threshold below this maximum. How would that affect the proportions algorithm? What would happen to the unused portion? Would it adapt to the slowed writeback and allocate it to some other writer? 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 |
