Jeff,
I recall seeting the IFS working (by some definition of "working") on
Eric JW's workstation in 2005. What specifically are the missing
features that must be implemented to complete the work?
Matt
Jeffrey Altman wrote:
The long term solution is clear. The OpenAFS community needs to move
away from the SMB Gateway model and replace it with a native Network
Provider / File System Filter model. Completing this work in such a
way that it is portable across Windows 2000 SP4 through Vista and
works on both 32-bit and 64-bit operating systems is going to be time
consuming and expensive. I hired a Windows file system and kernel
driver developer to review the work that has already been done and
help design an architecture that can support all of the required
platforms for the next ten years. We believe that this work can be
accomplished over a period of ten months provided that the necessary
financial resources ($250,000 - $300,000) can be acquired.
The long term benefits of getting rid of the SMB gateway are:
(1) the use of the Microsoft Loopback Adapter will no longer be required
(2) all of the problems associated with the CIFS client timeout issues
will be removed. this will not only improve performance but will
solve all of the "delayed write" and "network path no longer
available" errors.
(3) performance gains. There is significant time delays and CPU
load added to each transaction as a result of the CIFS client and
SMB server both involving the SMB/NetBIOS/TCP/IP stack.
If your organization is in a position to assist us in financing this
work, please contact me off-list.
Jeffrey Altman
OpenAFS Gatekeeper/Elder
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
