Searched full:peer (Results 1 – 25 of 71) sorted by relevance
123
| /Documentation/driver-api/ |
| D | ntb.rst | 14 peer. Doorbell registers provide a way for peers to send interrupt events.
15 Memory windows allow translated read and write access to the peer memory.
43 configured by the peer, on the peer ntb port. The first type is
48 Memory: Local NTB Port: Peer NTB Port: Peer MMIO:
57 3) somehow notify a peer device of performed initialization, 4) peer device
62 initialized by a peer device, is depicted on the figure::
66 Memory: Local NTB Port: Peer NTB Port: Peer MMIO:
74 1) allocate a memory region, 2) somehow deliver a translated address to a peer
75 device, 3) peer puts the translated address to NTB config, 4) peer device maps
85 3) Send the translated address and memory window index to a peer device
[all …]
|
| /Documentation/security/ |
| D | SCTP.rst | 77 addresses for reaching a peer
88 SCTP_SET_PEER_PRIMARY_ADDR - Request peer sets address as
101 then the following *_PARAM_*'s are sent to the peer in an
124 Called when a COOKIE ACK is received, and the peer secid will be
148 SCTP peer endpoint "Z".
152 SCTP peer endpoint "A" is asking
155 to set the peer label if first
174 to set the peer label. |
212 IF this is the first association on ``@asoc->base.sk``, then set the peer
213 sid to that in ``@skb``. This will ensure there is only one peer sid
[all …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | ti,usb8041.yaml | 31 peer-hub:
34 phandle to the peer hub on the controller.
39 - peer-hub
56 peer-hub = <&hub_3_0>;
64 peer-hub = <&hub_2_0>;
|
| D | vialab,vl817.yaml | 32 peer-hub:
35 phandle to the peer hub on the controller.
41 - peer-hub
58 peer-hub = <&hub_3_0>;
67 peer-hub = <&hub_2_0>;
|
| D | ti,usb8020b.yaml | 31 peer-hub:
34 phandle to the peer hub on the controller.
39 - peer-hub
56 peer-hub = <&hub_3_0>;
65 peer-hub = <&hub_2_0>;
|
| D | cypress,hx3.yaml | 48 peer-hub:
51 phandle to the peer hub on the controller.
56 - peer-hub
74 peer-hub = <&hub_3_0>;
84 peer-hub = <&hub_2_0>;
|
| D | genesys,gl850g.yaml | 29 peer-hub:
50 peer-hub: false
62 peer-hub: true
93 peer-hub = <&hub_3_0>;
102 peer-hub = <&hub_2_0>;
|
| D | realtek,rts5411.yaml | 34 peer-hub:
37 phandle to the peer hub on the controller.
71 - peer-hub
89 peer-hub = <&hub_3_0>;
104 peer-hub = <&hub_2_0>;
|
| D | microchip,usb5744.yaml | 46 peer-hub:
49 phandle to the peer hub on the controller.
71 peer-hub: false
98 peer-hub = <&hub_3_0>;
107 peer-hub = <&hub_2_0>;
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-usbip-vudc | 24 with peer
33 connection peer. It is done by writing to this
35 associated with a connection to remote peer who
|
| D | sysfs-bus-pci | 401 If the device has any Peer-to-Peer memory registered, this
409 If the device has any Peer-to-Peer memory registered, this
417 If the device has any Peer-to-Peer memory registered, this
427 of Peer-to-Peer memory for use in Peer-to-Peer transactions.
429 files for Peer-to-Peer copies.
508 be unbound from the device and peer devices under the same
|
| /Documentation/admin-guide/blockdev/drbd/ |
| D | figures.rst | 28 .. kernel-figure:: peer-states-8.dot
29 :alt: peer-states-8.dot
|
| D | disk-states-8.dot | 15 Failed -> Diskless [ label = "sending notify to peer" ]
|
| /Documentation/networking/ |
| D | mptcp-sysctl.rst | 12 resent to an MPTCP peer that has not acknowledged a previous
25 sent to the peer at connection time, and whether such join requests are
108 link with high BER or peer pausing the data processing.
|
| D | ipsec.rst | 36 when sending non-compressed packet to the peer (whether or not packet len
41 The result is much more wired to the user when ping peer with different
|
| D | tls-handshake.rst | 12 addition to peer authentication.
114 with serial numbers of keys containing the peer identities it wishes
125 The handshake agent presents no peer identity information to the remote
187 | -EACCESS | Remote peer rejected the handshake or |
200 remote peer's identity or the value TLS_NO_PEERID if the session is not
|
| D | tcp_ao.rst | 87 Q: Can an old MKT exist forever and be used by another peer?
103 an outdated key may become a security issue and as a peer may
107 and the kernel will atomically delete the old key, even if the peer is
108 still requesting it. There are no guarantees for force-delete as the peer
156 Q: What happens when RNextKeyID requested by a peer is unknown? Should
168 change, or is it triggered by a request from the remote peer? Is it set by the
249 the peer doesn't respect RNextKeyID; moving more code to userspace, especially
304 only when the peer ignores RNextKeyID and keeps requesting/using an old key.
316 peer and/or sndid/rcvid, VRF L3 interface or get current_key/rnext_key.
376 The reverse is valid as well: if userspace adds a new key for a peer on
[all …]
|
| D | tipc.rst | 26 to monitor the continuous existence of peer sockets? And yet without the
68 the peer node's availability.
80 multicast, when any of those services are available. If not, configured peer
|
| /Documentation/netlink/specs/ |
| D | handshake.yaml | 63 name: peer-identity
109 - peer-identity
|
| /Documentation/driver-api/pci/ |
| D | p2pdma.rst | 4 PCI Peer-to-Peer DMA Support
9 called Peer-to-Peer (or P2P). However, there are a number of issues that
|
| /Documentation/filesystems/ |
| D | sharedsubtree.rst | 261 A 'peer group' is defined as a group of vfsmounts that propagate
267 'peer group'.
275 to the same peer group. Anything mounted or unmounted under
276 /mnt or /tmp reflect in all the other mounts of its peer
299 has its own peer group too. This vfsmount receives propagation
301 events to its 'peer group' and to its slave vfsmounts.
304 peer group, and this peer-group is a slave of some other
305 peer group.
348 * if the shared mount is the only mount in its peer group, making it
391 'B'. And finally the peer-group of 'C' is merged with the peer group
[all …]
|
| /Documentation/driver-api/rapidio/ |
| D | rio_cm.rst | 63 Accepts a connection request from peer on the specified
69 Sends a connection request to a remote peer/channel.
84 to the remote peer.
|
| /Documentation/PCI/endpoint/ |
| D | pci-vntb-function.rst | 48 3) Peer Scratchpad Registers
76 | Peer Span Space | Span Space |
82 | Span Space | Peer Span Space |
|
| D | pci-ntb-function.rst | 53 3) Peer Scratchpad Registers
211 2) Peer Scratchpad: Remote host's register space.
227 There are 5 or more distinct regions (config, self scratchpad, peer
241 BAR2 Peer Scratchpad
262 BAR1 Peer Scratchpad
294 The peer host (HOST2 connected to EP controller 2) can also access this
295 scratchpad region (peer scratchpad) using BAR1 of EP controller 2. This
|
| /Documentation/driver-api/usb/ |
| D | power-management.rst | 654 In addition to these files some ports may have a 'peer' link to a port on
656 hi-speed peer::
658 $prefix/3-1:1.0/3-1-port1/peer -> ../../../../usb2/2-1/2-1:1.0/2-1-port1
659 ../../../../usb2/2-1/2-1:1.0/2-1-port1/peer -> ../../../../usb3/3-1/3-1:1.0/3-1-port1
662 peer ports are simply the hi-speed and superspeed interface pins that
663 are combined into a single usb3 connector. Peer ports share the same
671 before their superspeed peer is permitted to power-off. The implication is
673 not cause the port to power-off until its highspeed peer has gone to its
678 highspeed peer.
771 echo 0 > peer/power/pm_qos_no_power_off # if it exists
|
123