apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Laurie <...@algroup.co.uk>
Subject Re: cvs commit: apr/memory/unix apr_sms.c
Date Sat, 09 Jun 2001 17:34:21 GMT
Luke Kenneth Casson Leighton wrote:
> uh... i thought i should point out: the original proposal
> i recommended for the sms locking routine should pass
> in the area of memory to be locked and its length,
> and ditto for the unlocking.


> in this way, let's say you do mmap on a file, you can
> use posix locking as the implementation of the locking
> on the memory.
> [or can you?  i dunno, for sure :) ]

I believe so.

> and, if the argument is NULL, it means ' do a Global Lock'.
> if the unlock() argument is NULL, it means 'do a Global
> Unlock - i.e. free all locks'.

And if the locking mechanism doesn't support regions? (This is
particularly important if you allow unlocking of subregions). The
obvious answer being that we implement them in APR, of course.




"There is no limit to what a man can do or how far he can go if he
doesn't mind who gets the credit." - Robert Woodruff

View raw message