| 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
| ||
|
Message-ID: <20080123144717.GS8075@agk.fab.redhat.com> Date: Wed, 23 Jan 2008 14:47:17 +0000 From: Alasdair G Kergon <agk@...hat.com> To: Ryo Tsuruta <ryov@...inux.co.jp> Cc: linux-kernel@...r.kernel.org, dm-devel@...hat.com, containers@...ts.linux-foundation.org, virtualization@...ts.linux-foundation.org, xen-devel@...ts.xensource.com Subject: Re: [dm-devel] [PATCH 0/2] dm-band: The I/O bandwidth controller: Overview On Wed, Jan 23, 2008 at 09:53:50PM +0900, Ryo Tsuruta wrote: > Dm-band gives bandwidth to each job according to its weight, > which each job can set its own value to. > At this time, a job is a group of processes with the same pid or pgrp or uid. It seems to rely on 'current' to classify bios and doesn't do it until the map function is called, possibly in a different process context, so it won't always identify the original source of the I/O correctly: people need to take this into account when designing their group configuration and so this should be mentioned in the documentation. I've uploaded it here while we consider ways we might refine the architecture and interfaces etc.: http://www.kernel.org/pub/linux/kernel/people/agk/patches/2.6/editing/dm-add-band-target.patch Alasdair -- agk@...hat.com -- 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/
Powered by blists - more mailing lists