On Wed, Aug 28, 2019 at 3:04 PM Steve French <smfrench@xxxxxxxxx> wrote: > > Increases performance a lot in cases where we know that the share is > not changing Good idea but we can do it without adding a new mount option. Instead of "cache=ro" I think we should look at the WRITE bit in the tree connect response access mask since this should tell us if the share is read-only server-side or not. If the share is thus read-only we should then have that reflected in the "ro" mount option. I.e. * use TreeConnect/AccessMaks/WRITE flag to enable this more aggressive caching and not a mount option. * Probably also fail the mount if the WRITE flag is clear and the user did not specify "ro" as a mount option. ronnie > > > > -- > Thanks, > > Steve
