Lines Matching full:window

40 mainly used to perform the proper memory window initialization. Typically
41 there are two types of memory window interfaces supported by the NTB API:
55 So typical scenario of the first type memory window initialization looks:
58 maps corresponding outbound memory window so to have access to the shared
76 outbound memory window so to have access to the shared memory region.
82   1) Allocate memory for a shared window
83   2) Initialize memory window by translated address of the allocated region
84      (it may fail if local memory window initialization is unsupported)
85   3) Send the translated address and memory window index to a peer device
88   1) Initialize memory window with retrieved address of the allocated
89      by another device memory region (it may fail if peer memory window
91   2) Map outbound memory window
93 In accordance with this scenario, the NTB Memory Window API can be used as
106      the memory window with specified index for the defined peer device
108   5) Send translated base address (usually together with memory window
115      window. It may fail if retrieved address, for instance, exceeds
118      window so to have an access to the shared memory.
244 	If the peer ntb is to be accessed via a memory window, then use
245 	this memory window to access the peer ntb.  A value of zero or positive
250 	If the peer ntb is to be accessed via a memory window, and if
251 	the memory window is large enough, still allow the client to use the
252 	second half of the memory window for address translation to the peer.
255 	this 64 bit address on the bus between the NTB devices for the window