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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20081219183313.GB17113@us.ibm.com>
Date:	Fri, 19 Dec 2008 12:33:13 -0600
From:	"Serge E. Hallyn" <serue@...ibm.com>
To:	David Howells <dhowells@...hat.com>
Cc:	trond.myklebust@....uio.no, viro@...IV.linux.org.uk,
	nfsv4@...ux-nfs.org, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 03/45] Make the slow work pool configurable [ver #41]

Quoting David Howells (dhowells@...hat.com):
> Make the slow work pool configurable through /proc/sys/kernel/slow-work.
> 
>  (*) /proc/sys/kernel/slow-work/min-threads
> 
>      The minimum number of threads that should be in the pool as long as it is
>      in use.  This may be anywhere between 2 and max-threads.
> 
>  (*) /proc/sys/kernel/slow-work/max-threads
> 
>      The maximum number of threads that should in the pool.  This may be
>      anywhere between min-threads and 255 or NR_CPUS * 2, whichever is greater.
> 
>  (*) /proc/sys/kernel/slow-work/vslow-percentage
> 
>      The percentage of active threads in the pool that may be used to execute
>      very slow work items.  This may be between 1 and 99.  The resultant number
>      is bounded to between 1 and one fewer than the number of active threads.
>      This ensures there is always at least one thread that can process very
>      slow work items, and always at least one thread that won't.
> 
> Signed-off-by: David Howells <dhowells@...hat.com>

Acked-by: Serge Hallyn <serue@...ibm.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

Powered by Openwall GNU/*/Linux Powered by OpenVZ