Public/winfsp
1
0
Fork 0
mirror of https://github.com/winfsp/winfsp.git synced 2025-04-22 08:23:05 -05:00
Code Issues Packages Projects Releases Wiki Activity

doc; winfsp-ipc: update document

Browse Source
This commit is contained in:
Bill Zissimopoulos 2016-12-06 15:25:59 -08:00
parent 200de2a7f9
commit 25c687d5c5
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/winfsp-ipc.adoc
View File

@ -12,6 +12,7 @@ In the following we will also use the notation [U] to denote user mode processin
Consider then what happens when an OP issues a synchronous (non-overlapped), non-cached (non-buffered) WriteFile call.
ifdef::env-browser[]
[uml,file="winfsp-ipc/synchronous.png"]
--
hide footbox
@ -44,9 +45,12 @@ note over FSK, FSU #Salmon
Salmon color denotes WinFsp processing.
end note
--
endif::env-browser[]
ifndef::env-browser[image::winfsp-ipc/synchronous.png[]]
Let us now consider what happens when an OP issues an asynchronous (overlapped), non-cached (non-buffered) WriteFile call. This scenario does not show how the OP receives the WriteFile result.
ifdef::env-browser[]
[uml,file="winfsp-ipc/asynchronous.png"]
--
hide footbox
@ -85,6 +89,8 @@ note over FSK, FSU #Salmon
Salmon color denotes WinFsp processing.
end note
--
endif::env-browser[]
ifndef::env-browser[image::winfsp-ipc/asynchronous.png[]]
It should be noted that from the WinFsp perspective both cases look similar. WinFsp processing occurs:
@ -99,6 +105,7 @@ The TRANSACT calls are DeviceIoControl requests that the FS issues to WinFsp. A
Let us now consider what may happen with two simultaneous API Requests from two different processes. For example, two WriteFile requests for different files.
ifdef::env-browser[]
[uml,file="winfsp-ipc/multiple.png"]
--
hide footbox
@ -154,6 +161,8 @@ note over FSK, FSU #Salmon
Salmon color denotes WinFsp processing.
end note
--
endif::env-browser[]
ifndef::env-browser[image::winfsp-ipc/multiple.png[]]
Notice that it is possible for the FS to process multiple file system requests without context switching.