Content deleted Content added
m Date the maintenance tags or general fixes |
m formatting fix |
||
| (33 intermediate revisions by 23 users not shown) | |||
Line 1:
The '''Local Inter-Process Communication'''<ref name="ntdebugging">{{cite web|url=https://docs.microsoft.com/en-us/archive/blogs/ntdebugging/lpc-local-procedure-calls-part-1-architecture|title=LPC (Local procedure calls) Part 1 architecture|website=[[Microsoft Docs]]}}</ref> ('''LPC''', often also referred to as '''Local Procedure Call''' or '''Lightweight Procedure Call''') is an internal, undocumented [[inter-process communication]] facility provided by the [[Microsoft]] [[Windows NT]] [[Kernel (operating system)|kernel]] for lightweight [[inter-process communication|IPC]] between [[process (computing)|process]]es on the same computer. As of [[Windows Vista]], LPC has been rewritten as '''Asynchronous Local Inter-Process Communication'''<ref name="ntdebugging"/> ('''ALPC''', often also '''Advanced Local Procedure Call''') in order to provide a high-speed scalable communication mechanism required to efficiently implement [[User-Mode Driver Framework]] (UMDF), whose user-mode parts require an efficient communication channel with UMDF's components in the [[Architecture_of_Windows_NT#Executive|executive]].<ref>{{Harvcoltxt|Russinovich|Solomon|Ionescu|2009|p=201}}</ref>
The (A)LPC interface is part of Windows NT's undocumented [[Windows Native API|Native API]], and as such is not available to applications for direct use. However, it can be used indirectly in the following instances:
== Implementation ==▼
* when using the [[Microsoft RPC]] API to communicate locally, i.e. between the processes on the same machine
* by calling Windows APIs that are implemented with (A)LPC (see below)
For short messages (fewer than 304 bytes{{Fact|date=July 2008}}) the kernel copies the message buffers between processes. Longer messages require the creation of a shared memory section to transfer data, which the LPC service maps between the processes instead.▼
(A)LPC is implemented using kernel "port" objects, which are securable (with [[Access-control list|ACL]]s, allowing e.g. only specific [[Security Identifier|SID]]s to use them) and allow identification of the process on the other side of the connection. Individual messages are also securable: applications can set per-message SIDs, and also test for changes of the security context in the token associated with the (A)LPC message.
The typical communication scenario between the server and the client is as follows:
# A server process first creates a ''named server connection port'' object, and waits for clients to connect.
# A client requests a connection to that named port by sending a connect message.
# If the server accepts the connection, two ''unnamed'' ports are created:
#* ''client communication port'' - used by client threads to communicate with a particular server
#* ''server communication port'' - used by the server to communicate with a particular client; one such port per client is created
# The client receives a handle to the client communication port, and server receives a handle to the server communication port, and the inter-process communication channel is established.
(A)LPC supports the following three modes of message exchange between the server and client:<ref>{{Harvcoltxt|Russinovich|Solomon|Ionescu|2009|p=203}}</ref>
▲* For short messages (fewer than
* For messages longer than 256 bytes a shared memory section must be used to transfer data, which the (A)LPC service maps between the sending and receiving processes. First the sender places data into the shared memory, and then sends a notification (e.g. a small message, using the first method of (A)LPC) to the receiving process pointing to the sent data in the shared memory section.
* Server can directly read and write data from the client's address space, when the amount of data is too large to fit in a shared section.
ALPC has a performance advantage over the former LPC interface, as it can be configured to use [[Input/output completion port|I/O completion ports]] instead of synchronous request/reply mechanism that LPC exclusively uses.<ref>{{Harvcoltxt|Russinovich|Solomon|Ionescu|2009|p=204}}</ref> This enables ALPC ports high-speed communication which automatically balances the number of messages and threads. Additionally, ALPC messages can be batched together so as to minimize user-mode/kernel-mode switches.
==Known usage==
(A)LPC is used heavily in communication between internal subsystems in Windows NT. The Win32 subsystem
The [[Local Security Authority Subsystem Service]] (LSASS), [[Session Manager]] (SMSS)
As mentioned, Microsoft RPC can use (A)LPC as a transport when the client and server are both on the same machine. Many services that are designed to communicate only on the local computer use (A)LPC as the only transport through RPC. The implementation of remote [[
==See also==
▲The [[Local Security Authority Subsystem Service]] (LSASS), Session Manager (SMSS) [http://www.ppedia.com/p164_smss-smss.exe.htm], and Service Control Manager all use LPC ports directly to communicate with client processes.
* [[Doors (computing)|Doors]]
* [[Remote procedure call]]
==Notes==
▲Microsoft RPC can use LPC as a transport when the client and server are both on the same machine. Many services that are designed to communicate only on the local computer use LPC as the only transport through RPC. The implementation of remote [[object linking and embedding|OLE]] and [[Distributed Component Object Model|DCOM]] in many cases uses LPC for local communication as well.
{{reflist}}
==
* {{citation |first1=Prasad |last1=Dabak
*
==
*
* [http://www.zezula.net/en/prog/lpc.html LPC Communication]
| |||