linux-kernel - Re: [PATCH 1/3] i/o bandwidth controller documentation

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]

Message-ID: <17241648.1214150623059.JavaMail.oracle@acsmt302.oracle.com>
Date:	Sun, 22 Jun 2008 11:03:43 -0500 (CDT)
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	righi.andrea@...il.com
Cc:	axboe@...nel.dk, containers@...ts.linux-foundation.org,
	Balbir Singh <balbir@...ux.vnet.ibm.com>,
	Paul Menage <menage@...gle.com>,
	Carl Henrik Lunde <chlunde@...g.uio.no>, matt@...ehost.com,
	roberto@...it.it, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, Divyesh Shah <dpshah@...gle.com>
Subject: Re: [PATCH 1/3] i/o bandwidth controller documentation

--- Original Message ---
> Thanks Randy, I've applied all your fixes to my local
> documentation,
> next patchset version will include them. A few small comments
> below.
> 
> >> +WARNING: per-block device limiting rules always refer to the dev_t device
> >> +number. If a block device is unplugged (i.e. a USB device) the limiting rules
> >> +associated to that device persist and they are still valid if a new device is
> > 
> > associated with (?)
> 
> what about:
> 
> ...the limiting rules defined for that device...

Hi Andrea,

Yes, that's fine.

Thanks.

--
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/