Dear all,
on June 30, i wrote:
However, there might be NaviServer applications with nsvs out there,
for which the change of using rwlocks for nsv variables might lead to
a reduced performance. So we have in general the following options for
the forthcoming release:
a) hardwire nsvs to rwloc
On Wed, 1 Jul 2020 11:49:01 +0200
Gustaf Neumann wrote:
> There are already rwlocks in NaviServer since ages, used e.g. for epoch
> management, ADP tags, permissions. The current version uses as well
> rwlocks for nsv variables (most user visible part) and also for URLspace
> and connchan hand
On 01.07.20 10:53, Zoran Vasiljevic wrote:
I understand you added rwlocks elsewhere as well?
There are already rwlocks in NaviServer since ages, used e.g. for epoch
management, ADP tags, permissions. The current version uses as well
rwlocks for nsv variables (most user visible part) and also
On Wed, 1 Jul 2020 10:46:57 +0200
Gustaf Neumann wrote:
> Right now, the flag is set in the sources (nsthread/rwlock.c).
> For the release, a more user-friendly configure flag
> (--disable-nsvrwlock) would be appropriate.
I understand you added rwlocks elsewhere as well?
On 01.07.20 02:03, Maksym Zinchenko wrote:
Hello,first of all thank you for great work.
If I understood correctly on compile time we need to provide a
configuration option to compile NaviServer with mutex or rwlocks, so
option b sounds good and more than enough.
Right now, the flag is set in
Hello,first of all thank you for great work.
If I understood correctly on compile time we need to provide a
configuration option to compile NaviServer with mutex or rwlocks, so option
b sounds good and more than enough.
Default is rwlocks.
Correct me if I'm wrong.
On Tue, Jun 30, 2020 at 7:56 PM
Excellent work as always!
I'd go for the b. option.
> Am 30.06.2020 um 22:39 schrieb Gustaf Neumann :
>
>
> Dear all,
>
> some of you might have noticed the recent changes in the NaviServer
> repository concerning rwlocks. rwlocks support multiple concurrent readers
> and behave like mutex
