Is there a way to prevent write-back cache starvation caused by a process that monopolizes the cache?

Issue

There should be a possibility of limiting use of a cache on per-device basis, otherwise there is a possibility for a slow device (for example, a sluggish NFS client) to take all or the most of the write-back cache. There should be a limitation for particular device to use not more than the given percentage of the write-back cache. This is useful in situations where we want to avoid one device taking all or most of the write-back cache, for example in case of an NFS mount that is prone to get stuck, or a FUSE mount which cannot be trusted to play fair.