OpenSolaris

Printable Version Enter a New Search
Bug ID 4528299
Synopsis nfsd new architecture has interesting side effects for user and kernel stacks
State 10-Fix Delivered (Fix available in build)
Category:Subcategory network:nfs
Keywords s9-reviewed | scs9
Responsible Engineer Liane Praza
Reported Against 5.9
Duplicate Of
Introduced In
Commit to Fix s81_56
Fixed In s81_56
Release Fixed solaris_9(s81_56)
Related Bugs 1259585 , 4314534 , 4321796 , 4330007 , 4347131 , 4458285 , 4525403 , 4636250 , 4395201
Submit Date 16-November-2001
Last Update Date 16-November-2001
Description
 xxxxx@xxxxx.com 2001-11-16

The fix to

Bug Id: 4314534 Synopsis: NFS cannot be controlled by SRM
has resulted in a call to thread_create from user land
for each nfsd threads.

The call to thread_create uses default stacksize which
means that 1MB will be used. Since nfsd is a 32-bit process
it means that the number of active nfsd thread would be limited
by the available address space. Since the user level stack is
mostly unused, its would be easy to specify a small value for it.

There is a more important aspect to this though.
For each user thread, there will be a kernel lwp created
with default stack size: lwp_default_stksize.
This means that rpcmod:svc_default_stksize becomes ineffective
in controlling the kernel side stack associated with nfsd threads.

This could have serious implication to running NFS over VxFs and
possibly to  xxxxx  Cluster installation, PxFs and Tivoli. (see associated
bugid). Those product recommend tuning rpcmod:svc_default_stksize and this
now have no effect on nfsd threads.

 xxxxx@xxxxx.com 2001-11-16
Work Around
N/A
Comments
N/A