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 uf_lock of the device file
Bart Smaalders wrote:
Krishna Yenduri wrote:
...
This lock is uf_lock of the device file descriptor on which the ioctl
is being done. This contention is surprising to me because the
routine getf()
seems to be optimized for scaling.
Any ideas on what kind of solution is possible here? We ar
Mike,
> I've seen this clause before in other licenses (it did get removed when
> we asked).
As some additional incentive, we're working with the open source database
community on OSS benchmarks, and would really like them to use Studio
11 ...
--
Josh Berkus
PostgreSQL Lead
Sun Microsystems
S
Yuk. You're right. I will talk to the Studio11 folks, and see if we
can get this clause removed.
I've seen this clause before in other licenses (it did get removed when
we asked).
Let's see what we can do!
Mike
Eric M. Mantion wrote:
I hate to rain on the parade, but isn't this whole thr
