svn commit: r254380 - in head/sys: kern sys

[Colin Percival]

On 08/16/13 02:38, Ivan Voras wrote:
>> We have a single-writer / multiple-readers lock on *any particular byte*
>> of a vnode.  The rangelock code is what keeps track of this, and the
>> locking contention I was reducing was in the rangelock bookkeeping.
> 
> So, for example, if multiple processes or multiple threads read or
> write a file somewhat unintelligently (a small file, operations on the
> whole file, like in blogbench), they will effectively content for the
> byte 0, right?

There can be multiple reads or one write, so yes there would be contention
in that case.

-- 
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid