increasing stacksize,threads on io-net (npm-tcpip)

How can one increase the stacksize and number of threads for
npm-tcpip?
I tried
io-net -p tcpip stacksize=8192,threads=16

Is this the right syntax?
How can one monitor this?
pidin mem doesn’t reflect a change in these parameters to io-net’s
memory usage.

Would the number of threads available to npm-tpcip help to
support more simultaneous connections?
If not what is the effect of incrasing the number of threads
on npm-tcpip?

Using PE 6.2.0.
I tried this on x86 and a customer tried it on an 8260.

Alex Cellarius <acellarius@yahoo.com> wrote:

How can one increase the stacksize and number of threads for
npm-tcpip?
I tried
io-net -p tcpip stacksize=8192,threads=16

Is this the right syntax?
How can one monitor this?
pidin mem doesn’t reflect a change in these parameters to io-net’s
memory usage.

Would the number of threads available to npm-tpcip help to
support more simultaneous connections?
If not what is the effect of incrasing the number of threads
on npm-tcpip?

Using PE 6.2.0.
I tried this on x86 and a customer tried it on an 8260.

The syntax is correct. The default number of ‘threads’ is 48
so you are actually decreasing here. The number of threads
limits the number of blocking operations clients can perform at
a particluar time.
ie. you can have as many simultaneous connections as available memory
will allow but only X clients can be performing blocking operations at
a particular time where X is the number of threads.

The stacksize option was added for the case where people are designing
custom drivers / filters which are stack hungry. The default should
be sufficient for most cases.

-seanb