Re: [PATCH 00/27] IO-less dirty throttling v6

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Mar 03, 2011 at 02:45:05PM +0800, Wu Fengguang wrote:

[..]
> - serve as simple IO controllers: if provide an interface for the user
>   to set task_bw directly (by returning the user specified value
>   directly at the beginning of dirty_throttle_bandwidth(), plus always
>   throttle such tasks even under the background dirty threshold), we get
>   a bandwidth based per-task async write IO controller; let the user
>   scale up/down the @priority parameter in dirty_throttle_bandwidth(),
>   we get a priority based IO controller. It's possible to extend the
>   capabilities to the scope of cgroup, too.
> 

Hi Fengguang,

Above simple IO controller capabilities sound interesting and I was
looking at the patch to figure out the details. 

You seem to be mentioning that user can explicitly set the upper rate
limit per task for async IO. Can't really figure that out where is the
interface for setting such upper limits. Can you please point me to that.

Thanks
Vivek
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux