[PATCH][SAMBA3] use implicit oplocks to allow write caching

[James Peach]

Hi all,

The attached patch introduces a new IMPLICIT_OPLOCK modifier to standard
exclusive oplocks. The purpose of this is to allow write caching support
in the presence of CIFS clients that do not use oplocks.

An implicit oplock is an exclusive oplock that is taken without the
knowledge of the CIFS client. This means that when the oplock is broken,
the client must not be notified. Other than that, there is no change to
either the oplock implementation or semantics.

Any a write cache that was established while an exclusive oplock was
if force is removed once the oplock is broken.

Jeremy and Volker, can you please cast an eye over this?

-- 
James Peach | jpeach at sgi.com | SGI Australian Software Group
I don't speak for SGI.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: samba3-wcache-implicit-oplock.diff
Type: text/x-diff
Size: 5218 bytes
Desc: not available
Url : http://lists.samba.org/archive/samba-technical/attachments/20060320/55b1f6e2/samba3-wcache-implicit-oplock.bin