Lines Matching full:would

18 For OpenBMC, we would introduce a MCTP daemon, which implements the transport
45 The lower interface would be plugged in to one of a number of hardware-specific
46 binding implementations. Most of these would be included in the library source
52 this, the library would be written in portable C (structured in a way that can
68 socket. Each of these would register with the MCTP daemon to receive MCTP
69 messages of a certain type, and would transmit MCTP messages of that same type.
73 daemon would use a message queue to enable message reception/transmission to a
74 blocked daemon, but this would be of a limited size. Handlers whose sockets
75 exceed this queue would be disconnected from the daemon.
128 disjoint set. This would likely lead to unnecessary restrictions on the
130 frameworks used, etc). Also, this single-process approach would likely need more
134 as a socket-based interface. However, an alternative here would be to pass MCTP
145 For MCTP hardware bindings, we would develop channel-specific tests that would
148 For the OpenBMC MCTP daemon implementation, testing models would depend on the