Re: [perf-discuss] lock contention in ioctl() and scalability issues

2006-11-08 Thread Krishna Yenduri
Bart Smaalders wrote On 11/08/06 07:47,: ... A quick check with libmicro indicates Prakash's suggestion scales very nicely indeed, and will not change semantics at all. Just have each thread dup(2) its crypto fd and all the contention in getf will disappear. Yes. We also noticed the same re

Re: [perf-discuss] lock contention in ioctl() and scalability issues

2006-11-08 Thread Bart Smaalders
prakash sangappa wrote: The 'uf_lock' is a per 'fd' lock. Therefore, the application could possibly dup(2) the fd, to get one for each thread. That should help avoid the uf_lock contention. -Prakash. Krishna Yenduri wrote: Bart Smaalders wrote: Krishna Yenduri wrote: ... This lock is u

[perf-discuss] unsubscribe

2006-11-08 Thread Edgar Alburquerque
  ___ perf-discuss mailing list perf-discuss@opensolaris.org

[perf-discuss] filebench fails with "flowop openfile1 failed on line 1"

2006-11-08 Thread Atul Vidwansa
Hi, I am trying to use filebench1.64.5_s10_x86_sparc_PRERELEASE_pkg.tar.Z on S10u3 SPARC machine with fileserver personality and following options: bash-3.00# cat ufs_local.prof DEFAULTS { runtime = 180; dir = /mnt/ufs_local; stats = /stats/run1; filesystem = ufs;