| /openbmc/linux/net/rds/ |
| H A D | transport.c | 47 static struct rds_transport *transports[RDS_TRANS_COUNT]; variable
56 if (transports[trans->t_type]) in rds_trans_register()
60 transports[trans->t_type] = trans; in rds_trans_register()
72 transports[trans->t_type] = NULL; in rds_trans_unregister()
102 trans = transports[i]; in rds_trans_get_preferred()
121 trans = transports[t_type]; in rds_trans_get()
127 trans = transports[t_type]; in rds_trans_get()
157 trans = transports[i]; in rds_trans_stats_info_copy()
|
| /openbmc/phosphor-ipmi-flash/bmc/firmware-handler/ |
| H A D | firmware_handler.hpp | 104 * @param[in] transports - list of transports to support.
110 std::vector<DataHandlerPack>&& transports,
118 * @param[in] transports - list of transport types and their handlers
124 std::vector<DataHandlerPack>&& transports, in FirmwareBlobHandler() argument
127 transports(std::move(transports)), activeImage(activeImageBlobId), in FirmwareBlobHandler()
225 std::vector<DataHandlerPack> transports; member in ipmi_flash::FirmwareBlobHandler
|
| H A D | firmware_handler.cpp | 41 std::vector<DataHandlerPack>&& transports, ActionMap&& actionPacks) in CreateFirmwareBlobHandler() argument
49 if (transports.empty()) in CreateFirmwareBlobHandler()
71 std::move(firmwares), blobs, std::move(transports), in CreateFirmwareBlobHandler()
423 auto d = std::find_if(transports.begin(), transports.end(), in open()
427 if (d == transports.end()) in open()
|
| /openbmc/linux/net/sctp/ |
| H A D | associola.c | 377 transport = list_entry(pos, struct sctp_transport, transports); in sctp_association_free()
499 list_del_rcu(&peer->transports); in sctp_assoc_rm_peer()
505 transport = list_entry(pos, struct sctp_transport, transports); in sctp_assoc_rm_peer()
607 /* An UNKNOWN state is only set on transports added by in sctp_assoc_add_peer()
608 * user in sctp_connectx() call. Such transports should be in sctp_assoc_add_peer()
720 list_add_tail_rcu(&peer->transports, &asoc->peer.transport_addr_list); in sctp_assoc_add_peer()
748 transport = list_entry(pos, struct sctp_transport, transports); in sctp_assoc_del_peer()
764 /* Cycle through all transports searching for a peer address. */ in sctp_assoc_lookup_paddr()
767 transports) { in sctp_assoc_lookup_paddr()
775 /* Remove all transports except a give one */
[all …]
|
| H A D | outqueue.c | 214 transports) { in __sctp_outq_teardown()
438 transports) { in sctp_prsctp_prune()
791 /* These transports have chunks to send. */
814 * transports created. in sctp_outq_select_transport()
860 /* Are we switching transports? Take care of transport locks. */ in sctp_outq_select_transport()
872 /* We've switched transports, so apply the in sctp_outq_select_transport()
1000 /* Switch transports & prepare the packet. */ in sctp_outq_flush_rtx()
1269 list_for_each_entry(transport, transport_list, transports) in sctp_outq_sack()
1304 transports) { in sctp_outq_sack()
1337 list_for_each_entry(transport, transport_list, transports) { in sctp_outq_sack()
[all …]
|
| /openbmc/linux/tools/virtio/linux/ |
| H A D | virtio_config.h | 12 * __virtio_test_bit - helper to test feature bits. For use by transports.
25 * __virtio_set_bit - helper to set feature bits. For use by transports.
36 * __virtio_clear_bit - helper to clear feature bits. For use by transports.
|
| /openbmc/linux/net/9p/ |
| H A D | Kconfig | 24 This builds support for transports over TCP, Unix sockets and
31 This builds support for a transports between
|
| /openbmc/qemu/qapi/ |
| H A D | virtio.json | 223 # "transports": [],
240 # "transports": [
249 # "transports": [
290 # "transports": []
302 # "transports": [
313 # "transports": [
348 # "transports": [
390 # "transports": [
421 # "transports": [
485 # @transports: List of transport features of the virtio device
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | KeyPolicy.v1_0_1.json | 241 "description": "The security transports that this key policy allows.",
252 …transports that this key policy allows. The absence of the property shall indicate any security t…
343 "description": "The NVMe security transports that a key is allowed to use.",
356 …"longDescription": "This enumeration shall list the NVMe security transports that a key is allowed…
|
| /openbmc/qemu/docs/system/arm/ |
| H A D | vexpress.rst | 56 - QEMU provides 4 virtio-mmio virtio transports; these start at
60 suitable entries describing these transports for the guest.
|
| /openbmc/linux/arch/um/drivers/ |
| H A D | Kconfig | 247 This driver provides tap, raw, gre and l2tpv3 network transports
284 at least one UML with one of the other transports to act as a
329 unlike other network transports that can handle all Ethernet
332 other transports, SLiRP works without the need of root level
|
| /openbmc/linux/Documentation/virt/uml/ |
| H A D | user_mode_linux_howto_v2.rst | 233 * All transports which have tso and checksum offloads can deliver speeds
236 * All transports which have multi-packet rx and/or tx can deliver pps
239 * All legacy transports are generally limited to ~600-700MBit and 0.05Mps.
257 For newer network drivers like the vector transports, ``root`` privilege
271 Configuring vector transports
274 All vector transports support a similar syntax:
284 These options are common for all transports:
301 corresponding UML transports (raw, tap, hybrid) in order for networking to
315 * ``ifname=str`` Transports which bind to a local network interface
318 * ``src, dst, src_port, dst_port`` - all transports which use sockets
[all …]
|
| /openbmc/linux/Documentation/networking/ |
| H A D | rds.rst | 26 transports. The current implementation used to support RDS over TCP as well
268 sages on sockets. The dense bitmaps let transports send the
396 (though the concept can be extended to other transports). The classical
416 Transports such as TCP that are multipath capable may then set up a
420 Transports announce themselves as multipath capable by setting the
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | KeyPolicy_v1.xml | 114 …<Annotation Term="OData.Description" String="The security transports that this key policy allows."…
115 …transports that this key policy allows. The absence of the property shall indicate any security t…
164 …<Annotation Term="OData.Description" String="The NVMe security transports that a key is allowed to…
165 …LongDescription" String="This enumeration shall list the NVMe security transports that a key is al…
|
| /openbmc/openbmc/poky/meta/recipes-graphics/xorg-lib/ |
| H A D | xtrans_1.5.2.bb | 6 Use of this API should allow the addition of new types of transports and \
|
| /openbmc/linux/drivers/input/rmi4/ |
| H A D | Makefile | 17 # Transports
|
| /openbmc/qemu/docs/devel/ |
| H A D | virtio-backends.rst | 17 VirtIO Transports
20 VirtIO supports a number of different transports. While the details of
|
| /openbmc/phosphor-ipmi-flash/bmc/firmware-handler/test/ |
| H A D | firmware_stat_unittest.cpp | 18 * tools by reporting that all transports are supported. */
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | vm_sockets.h | 109 * transports too.
124 * this would be useful for other transports too.
|
| /openbmc/qemu/hw/virtio/ |
| H A D | Kconfig | 43 # not all virtio transports support memory devices; if none does,
|
| /openbmc/linux/drivers/infiniband/ulp/ipoib/ |
| H A D | Kconfig | 7 transports IP packets over InfiniBand so you can use your IB
|
| /openbmc/linux/include/linux/sunrpc/ |
| H A D | xprtsock.h | 53 * Connection of transports
|
| /openbmc/linux/net/vmw_vsock/ |
| H A D | Kconfig | 13 You should also select one or more hypervisor-specific transports
|
| /openbmc/linux/drivers/nvme/target/ |
| H A D | Kconfig | 13 You need to select at least one of the transports below to make this
|
| /openbmc/hiomapd/Documentation/ |
| H A D | protocol.md | 16 This document defines a protocol and several transports for flash access
39 transports, and does not cover the content or structure of the data read or
78 the protocol has grown further transports and naming the protocol by its
131 ## List of Transports
138 There are three documented transports for the protocol:
150 Implementations must choose to support one or more of the transports outlined in
270 transports to keep a compact representation in constrained implementations such
282 Several transports are defined for the protocol and are outlined below. The key
399 transports respectively. For the command identifier table the value in these
1377 The M, I, and D columns represent the Mailbox, IPMI and DBus transports
|