docs/167382: geli.8 out of sync after r226840 re: kernel threads

[John W. O'Brien]

>Number:         167382
>Category:       docs
>Synopsis:       geli.8 out of sync after r226840 re: kernel threads
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Apr 27 23:10:10 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator:     John W. O'Brien
>Release:        9-STABLE
>Organization:
Saltant Solutions
>Environment:
FreeBSD nippl.y.saltant.net 9.0-STABLE FreeBSD 9.0-STABLE #0: Mon Apr  9 07:44:49 EDT 2012     root at nippl.y.saltant.net:/usr/obj/usr/src/sys/NIPPL  amd64
>Description:
r226840 did not update description of affected behavior in geli(8) manpage.
>How-To-Repeat:
man geli
Search for "kern.geom.eli.threads".
Observe that following r226840, number of threads is not limited when, e.g., AESNI instructions are available.
>Fix:
Strike line stating that only one thread will be started when using hardware crypto acceleration.

Patch attached with submission follows:

Index: geli.8
===================================================================
--- geli.8	(revision 234740)
+++ geli.8	(working copy)
@@ -24,7 +24,7 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd March 4, 2012
+.Dd April 27, 2012
 .Dt GELI 8
 .Os
 .Sh NAME
@@ -692,7 +692,6 @@
 Specifies how many kernel threads should be used for doing software
 cryptography.
 Its purpose is to increase performance on SMP systems.
-If hardware acceleration is available, only one thread will be started.
 If set to 0, a CPU-pinned thread will be started for every active CPU.
 .It Va kern.geom.eli.batch : No 0
 When set to 1, can speed-up crypto operations by using batching.


>Release-Note:
>Audit-Trail:
>Unformatted: