A packet or streams layer for GENSEC/SASL?

Jeremy Allison jra at samba.org
Tue Feb 7 15:23:20 GMT 2006


On Tue, Feb 07, 2006 at 10:00:54AM -0500, David Collier-Brown wrote:
> 
>   Thus this possibility: Samba uses the size it thinks
> best. For oplocked files, which have a high probability
> of being read and written sequentially, Samba might
> use a fairly large value. A user could request a different
> size on a per-share basis.

That *is* the write cache code.

>   I suspect this would lead to a path where the write
> cache code falls out of use and can be deprecated, and

Nope, because as soon as Samba uses a different read/write
size than the client requested then you've re-invented the
(working) write cache code.

Jeremy.


More information about the samba-technical mailing list