[OpenAFS-win32-devel] Urgent! Anyone could give me a picture of openafs client for windows architecture?

[hedgepiggy]

Thank you Bharat and Jeffrey. Thanks for your explanation.
But there is still another question confused me. You meant that filesystem
request would be passed by NetBIOS in SMB packet to SMB server. But how
could NetBIOS receive this filesystem request(read/write)?
Does it receive request from I/O Manager? Then how could I/O Manager know it
should be passed to NetBIOS?

I am a fresher to NetBIOS. So if you could take a read operation process for
example, I would very very appreciate it!!! Thank you very much!


Bharat Kulkarni wrote:
> 
> I will be giving a lil bit of openafs on windows ( usermode
> distributed filesystem )
> 
> Openafs currently following two implementations for windows.
> 
> one is .. open afs is completely implemented in userspace which do not
> have any kernel mode module.
> 
> and another way is using the remote file system driver.
> ----
> I will be writing about the earlier part of the implementation.
> 
> when you install openafs client on your windows machine,
> it basically gets loaded as a service (image file - afsservice.exe).
> 
> this service is nothing but your afs client.
> 
> afs client is nothing but a smb server.
> 
> while starting the service ( during installation ) this service
> registers its name to the netbios table on the same machine.
> 
> so when you get any read writes to the afs mapped drive.. those read
> writes would be wrapped into smb packets and those will be sent to the
> smb-server ( afs client - the service ) on the same machine ..
> 
> smb server parsed that request talks to the cache manger, if require,
> further forms rx protocol packets and talks to the file manager over
> the network.
> ------
> 
> To consider the letter way of openafs implementation, using a proper
> kernel mode module,
> 
> in this approach, openafs would have a remote filesystem driver.
> 
> which will get loaded over the portocol stack using the tdi interface.
> 
> It will register it self with mup, there by will register itself in
> service providers list.
> ( OpenAFSdaemon in services - registry entry)
> 
> and that's how the read write calls can come to service provider list
> .. openafs will claim for it .. and accordingly io manager will send
> the further request to the openafs redirector.
> 
> 
> 
> On Fri, Apr 24, 2009 at 5:33 PM, hedgepiggy <hedgepiggy@gmail.com> wrote:
>>
>> What is the kernel module of openafs client for windows?
>> where did afs place it in the existing windows kernel layers.
>> Is it a filesystem driver or a filter driver?
>> Anyone could give me a picture of how openafs client for windows places
>> itself in the existing windows kernel architecture?
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Urgent%21-Anyone-could-give-me-a-picture-of-openafs-client-for-windows-architecture--tp23215059p23215059.html
>> Sent from the OpenAFS - Windows Dev mailing list archive at Nabble.com.
>>
>> _______________________________________________
>> OpenAFS-Win32-devel mailing list
>> OpenAFS-Win32-devel@openafs.org
>> http://lists.openafs.org/mailman/listinfo/openafs-win32-devel
>>
> _______________________________________________
> OpenAFS-Win32-devel mailing list
> OpenAFS-Win32-devel@openafs.org
> http://lists.openafs.org/mailman/listinfo/openafs-win32-devel
> 
> 

-- 
View this message in context: http://www.nabble.com/Urgent%21-Anyone-could-give-me-a-picture-of-openafs-client-for-windows-architecture--tp23215059p23217749.html
Sent from the OpenAFS - Windows Dev mailing list archive at Nabble.com.