/* PF/VF Mailbox state machine * * +----------+ connect() +----------+ * | CLOSED | --------------> | CONNECT | * +----------+ +----------+ * ^ ^ | * | rcv: rcv: | | rcv: * | Connect Disconnect | | Connect * | Disconnect Error | | Data * | | | * | | V * +----------+ disconnect() +----------+ * |DISCONNECT| <-------------- | OPEN | * +----------+ +----------+ * * The diagram above describes the PF/VF mailbox state machine. There * are four main states to this machine. * Closed: This state represents a mailbox that is in a standby state * with interrupts disabled. In this state the mailbox should not * read the mailbox or write any data. The only means of exiting * this state is for the system to make the connect() call for the * mailbox, it will then transition to the connect state. * Connect: In this state the mailbox is seeking a connection. It will * post a connect message with no specified destination and will * wait for a reply from the other side of the mailbox. This state * is exited when either a connect with the local mailbox as the * destination is received or when a data message is received with * a valid sequence number. * Open: In this state the mailbox is able to transfer data between the local * entity and the remote. It will fall back to connect in the event of * receiving either an error message, or a disconnect message. It will * transition to disconnect on a call to disconnect(); * Disconnect: In this state the mailbox is attempting to gracefully terminate * the connection. It will do so at the first point where it knows * that the remote endpoint is either done sending, or when the * remote endpoint has fallen back into connect.
*/ enum fm10k_mbx_state {
FM10K_STATE_CLOSED,
FM10K_STATE_CONNECT,
FM10K_STATE_OPEN,
FM10K_STATE_DISCONNECT,
};
/* PF/VF Mailbox header format * 3 2 1 0 * 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ * | Size/Err_no/CRC | Rsvd0 | Head | Tail | Type | * +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ * * The layout above describes the format for the header used in the PF/VF * mailbox. The header is broken out into the following fields: * Type: There are 4 supported message types * 0x8: Data header - used to transport message data * 0xC: Connect header - used to establish connection * 0xD: Disconnect header - used to tear down a connection * 0xE: Error header - used to address message exceptions * Tail: Tail index for local FIFO * Tail index actually consists of two parts. The MSB of * the head is a loop tracker, it is 0 on an even numbered * loop through the FIFO, and 1 on the odd numbered loops. * To get the actual mailbox offset based on the tail it * is necessary to add bit 3 to bit 0 and clear bit 3. This * gives us a valid range of 0x1 - 0xE. * Head: Head index for remote FIFO * Head index follows the same format as the tail index. * Rsvd0: Reserved 0 portion of the mailbox header * CRC: Running CRC for all data since connect plus current message header * Size: Maximum message size - Applies only to connect headers * The maximum message size is provided during connect to avoid * jamming the mailbox with messages that do not fit. * Err_no: Error number - Applies only to error headers * The error number provides an indication of the type of error * experienced.
*/
/* HNI/SM Mailbox FIFO format * 3 2 1 0 * 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 * +-------+-----------------------+-------+-----------------------+ * | Error | Remote Head |Version| Local Tail | * +-------+-----------------------+-------+-----------------------+ * | | * . Local FIFO Data . * . . * +-------+-----------------------+-------+-----------------------+ * * The layout above describes the format for the FIFOs used by the host * network interface and the switch manager to communicate messages back * and forth. Both the HNI and the switch maintain one such FIFO. The * layout in memory has the switch manager FIFO followed immediately by * the HNI FIFO. For this reason I am using just the pointer to the * HNI FIFO in the mailbox ops as the offset between the two is fixed. * * The header for the FIFO is broken out into the following fields: * Local Tail: Offset into FIFO region for next DWORD to write. * Version: Version info for mailbox, only values of 0/1 are supported. * Remote Head: Offset into remote FIFO to indicate how much we have read. * Error: Error indication, values TBD.
*/
/* version number for switch manager mailboxes */ #define FM10K_SM_MBX_VERSION 1 #define FM10K_SM_MBX_FIFO_LEN (FM10K_MBMEM_PF_XOR - 1)
/* All error messages returned by mailbox functions * The value -511 is 0xFE01 in hex. The idea is to order the errors * from 0xFE01 - 0xFEFF so error codes are easily visible in the mailbox * messages. This also helps to avoid error number collisions as Linux * doesn't appear to use error numbers 256 - 511.
*/ #define FM10K_MBX_ERR(_n) ((_n) - 512) #define FM10K_MBX_ERR_NO_MBX FM10K_MBX_ERR(0x01) #define FM10K_MBX_ERR_NO_SPACE FM10K_MBX_ERR(0x03) #define FM10K_MBX_ERR_TAIL FM10K_MBX_ERR(0x05) #define FM10K_MBX_ERR_HEAD FM10K_MBX_ERR(0x06) #define FM10K_MBX_ERR_SRC FM10K_MBX_ERR(0x08) #define FM10K_MBX_ERR_TYPE FM10K_MBX_ERR(0x09) #define FM10K_MBX_ERR_SIZE FM10K_MBX_ERR(0x0B) #define FM10K_MBX_ERR_BUSY FM10K_MBX_ERR(0x0C) #define FM10K_MBX_ERR_RSVD0 FM10K_MBX_ERR(0x0E) #define FM10K_MBX_ERR_CRC FM10K_MBX_ERR(0x0F)
/* size of buffer to be stored in mailbox for FIFOs */ #define FM10K_MBX_TX_BUFFER_SIZE 512 #define FM10K_MBX_RX_BUFFER_SIZE 128 #define FM10K_MBX_BUFFER_SIZE \
(FM10K_MBX_TX_BUFFER_SIZE + FM10K_MBX_RX_BUFFER_SIZE)
/* minimum and maximum message size in dwords */ #define FM10K_MBX_MSG_MAX_SIZE \
((FM10K_MBX_TX_BUFFER_SIZE - 1) & (FM10K_MBX_RX_BUFFER_SIZE - 1)) #define FM10K_VFMBX_MSG_MTU ((FM10K_VFMBMEM_LEN / 2) - 1)
#define FM10K_MBX_INIT_TIMEOUT 2000 /* number of retries on mailbox */ #define FM10K_MBX_INIT_DELAY 500 /* microseconds between retries */
struct fm10k_mbx_info { /* function pointers for mailbox operations */ struct fm10k_mbx_ops ops; conststruct fm10k_msg_data *msg_data;
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.