linux-kernel - Re: Blkio: Apply two policies on one IO process

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 29 Mar 2011 12:44:45 -0400
From:	Vivek Goyal <vgoyal@...hat.com>
To:	Lina Lu <lulina_nuaa@...mail.com>
Cc:	linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: Blkio: Apply two policies on one IO process

On Wed, Mar 30, 2011 at 12:00:16AM +0800, Lina Lu wrote:
> Hi Vivek,
>       As the weight and throttle policies are on different layers, someone can apply 
> these two policies on one IO pid at one time. And the IO bandwidth will be controlled
> with the more stringent policy.
>       If someone first set two policies on one pid, then want to remove the weight
> policy, he must first echo the pid to parent dir's tasks, then echo the throttle policy
> to parent dir's blkio.throttle_xx_xx_device. These steps seen to be cumbersome.
>       This is because the weight policy can be applied independence, but the throttle
> policy is always accompany with the weight policy(default 500). I think it will be 
> better that these policies are independent of each other. What is your opinion?
>       Additional, do you recommend applying two policies on one IO process?

How do you want to make these independent?

- If one does not want weight based policy, one can change IO scheduler
  to deadline.

- If one does not want throttling policy, do not apply throttling limits.

Thanks
Vivek
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/