protocol cifs oopen extension

add <extension>	Specifies a list of file extensions to include in overlapping opens optimization.
setting-always <policy>	Specifies the policy to force on the specified file extension: • allow - Allows overlapping opens to enable better performance. • deny - Denies overlapping opens on the specified file extension.
modify <extension> setting <policy>	Modifies the policy setting for the specified file extension: • allow - Allows overlapping opens to enable better performance. • deny - Denies overlapping opens on the specified file extension.
remove <extension>	Removes a file extension from the special case list (that is, do not optimize the specified file extension).

Enable overlapping opens to obtain better performance with applications that perform multiple opens on the same file. With overlapping opens enabled, the SteelHead optimizes data to which exclusive access is available (in other words, when locks are granted). When an oplock is not available, the SteelHead does not perform application-level latency optimization but still performs SDR and compression on the data, as well as TCP optimizations. If you do not enable this feature, the SteelHead still increases WAN performance, but not as effectively.

Enabling this feature on applications that perform multiple opens on the same file to complete an operation (for example, CAD applications) results in a performance improvement.

You specify a list of extensions you want to optimize using overlapping opens. You can also use this command to specify a list of extensions you do not want to optimize using overlapping opens.

If a remote user opens a file which is optimized using the overlapping opens feature and a second user opens the same file, the second user might receive an error if the file fails to go through a v3.x SteelHead or if it does not go through a SteelHead at all (for example, certain applications that are sent over the LAN). If this occurs, you should disable overlapping opens for those applications.