TW201404097A - Techniques for using an assigned switch identification at an input/output device - Google Patents

Abstract

Examples are disclosed for assigning a switch identification to data received at an input/output device coupled to a host device. In some examples, the data may be associated with a virtual station interface (VSI) for a virtual machine implemented at the host device. For these examples, a switch identification may be assigned to the data based on an assigned port identifier, identification information for the data, or an originator of at least a portion of the identification information. The assigned switch identification may then be used as part of a lookup table to determine one or more actions for processing the data at the input/output device. Other examples are described and claimed.

Description

Techniques for identifying the input/output devices using assigned switches

The present invention is directed to techniques for identifying an input/output device using an assigned switch.

Background of the invention

An input/output (I/O) device, such as a network interface card (NIC), can be coupled to a computing platform or host device deployed in the server-network edge at the server-network edge At the end, the server domain ends and the external network domain begins. A known way to implement switching logic or circuitry at the NIC in these types of environments is via the use of a set of lookup tables. The lookup tables may identify portions of the material such as the packet header, and then, the actions may be defined in the lookup table based on the packet header. Lookup tables generally function well in NICs that implement switching circuits that connect all of the ports via a single handoff.

The proposed standard of the Institute of Electrical and Electronics Engineers (IEEE) describes the implementation of many switchers as Edge Virtual Bridging (EVB). Minute. The proposed standard has the title "IEEE Standard for Local and Metropolitan Area Networks - Virtual Bridged Local Area Networks - Amendment Edge Virtual Bridging" and is identified as IEEE 802.1Qbg - Draft 2.1 published on January 30, 2012 (hereinafter in "IEEE 802.1Qbg"). A NIC operating in accordance with IEEE 802.Qbg may need to implement separate dedicated handover enforcement entities for each logical or virtual port associated with the Ethernet network. Again, the NIC may need to implement an additional local switch instance for internal traffic between processing elements at the host device that may include a virtual machine (VM). In addition, a tandem switch implementation entity may be required to implement a Virtual Ethernet Bridge (VEB) or a Virtual Ethernet Port Aggregator (VEPA) within a single Ethernet network. ). For such multiple handover performers, the use of a separate lookup table for each handover executive may require a substantial quality NIC resource.

According to an embodiment of the present invention, a method is specifically provided, comprising: receiving data at an input/output device coupled to a host device, the data being maintained at a virtual station at the input/output device Associated with the interface, the virtual station interface is communicatively coupled to a virtual machine implemented at the host device, the data being transmitted from one of the virtual machine or a network element, the network element being a network communication link coupled to the input/output device; one of the assigned identifiers for transmitting the data at the input/output device, the identification information for the data, and the Identifying at least one of the sources of information and putting everything The change identification is assigned to the profile; the assigned switch identification is used as part of a lookup table to determine one or more actions for processing the data at the input/output device.

100‧‧‧ system

101, 700‧‧‧ host device

103-2‧‧‧ Entity

111, 112, 113, 114, 115, 116, 117, 118‧‧‧ virtual machine (VM)

111D, 112D, 113A, 114B, 115C, 116D, 117E, 118x‧‧‧ Virtual Station Interface (VSI)

130-1, 130-2, 130-3, 130-4‧‧‧埠

140‧‧‧Input/Output (I/O) devices

141, 143, 146, 147, 148, 149‧‧ virtual switchers (V.S.)

141-D‧‧‧Logical (L埠)

142‧‧‧Switch Manager

143A/B, 146C, 147D, 148E, 149x‧‧ links

144‧‧‧埠 Extender

144-1C, 144-2D‧‧‧E埠

145, 530, 760‧‧‧ memory

150-1, 150-2, 150-3, 150-4‧‧‧ communication links

160‧‧‧Network

200‧‧‧Instance switching identification structure

210, 220, 230‧‧‧ fields

300‧‧‧ Assigned Switch Identification Table

400‧‧‧ lookup table

510‧‧‧Switching logic

512‧‧‧ receiving characteristics

514‧‧‧ Assignment features

516‧‧‧ Find features

520‧‧‧Control logic

540‧‧‧Input/Output (I/O) interface

Block 610 to 680‧‧

705‧‧‧Super Supervisor

710‧‧‧ operating system

711‧‧‧ device driver

715‧‧‧User interface

720‧‧‧Application

730‧‧‧Network Input/Output (I/O) Devices

735, 754‧‧ interface

740‧‧‧User input/output (I/O) device

750‧‧‧Storage

770‧‧‧Central Processing Unit (CPU)

780‧‧‧ chipsets

790‧‧‧Communication (Comms)

Figure 1 illustrates an example system.

Figure 2 illustrates an example switch identification structure.

FIG. 3 illustrates an example assigned handover identification table.

Figure 4 illustrates an example lookup table.

Figure 5 illustrates a block diagram of an example architecture for a handover manager.

Figure 6 illustrates an example flow diagram for assigning handover identification.

Figure 7 illustrates an example system diagram for a host device.

Detailed description of the preferred embodiment

As contemplated by the present invention, when a separate lookup table is used for each handover execution individual, multiple handover execution individuals may need real quality NIC resources when implementing the EVB. Also, the handover execution individual in the virtual handover environment can be associated with the dynamic association. Due to dynamic composition, assigning a separate lookup table for each possible handover execution individual may require too much resources and may also define possible combinations, since a given NIC has limited resources to support such separate lookup tables.

In some examples, techniques are implemented for assigning handover identification to data received at an input/output device coupled to a host device. For such instances, the data can be associated with a virtual station interface (VSI) maintained at the I/O device, and the VSI can be communicatively coupled. Connect to the virtual machine implemented at the host device. For such instances, the data may have been sent from one of a virtual machine or a network element that can be coupled to the I/O device via a network communication link. The handover identification can be assigned to the profile based on the originator for the at least a portion of the assigned 埠 identifier for the data received at the I/O device, the identification information for the data, and the identification information. The assigned handover identification can be used as part of a lookup table to determine one or more actions for processing data at the I/O device.

Figure 1 illustrates an example first system. As shown in FIG. 1, an example first system includes system 100. System 100 can include a host device 101 coupled to an input/output (I/O) device 140. As shown in FIG. 1, the I/O device 140 can be connected via various virtual station interfaces (VSI) 111D, 112D, 113A included in virtual switches (VS) 141, 143, 146, 147, 148, and 149. 114B, 115C, 116D, 117E and 118x are coupled to the host device 101 ("x" indicates association with a data channel still to be established). The various VSIs included with such virtual switchers can be separately configured to be coupled to virtual machines (VMs) 111-118 as shown in FIG. 1, and can enable data (eg, data packets or data frames) The form can be received/transmitted from VMs 111 through 118 to VMs 111 through 118. For such instances, VMs 111 through 118 can be configured or configured to be implemented using computing resources maintained at host device 101. Any number of virtual switchers can be associated with any number of VSIs and communicatively coupled to any number of VMs and/or virtual machine managers (super supervisors).

According to some examples, as shown in FIG. 1, a logical volume (L埠) 141-D is shown as being included in the virtual switcher 141. L埠141-D can act as energy The logic 耦 is coupled to the data channel D. As mentioned more below, data channel D can be configured to route data between VM 111 and VM 112. For example, routing of data can be via respective VSIs 111 and 112, as shown in FIG.

Also, as shown in FIG. 1, communication links 150-1 through 150-4 can couple network elements included in network 160 to host device 101 via respective ports 130-1 through 130-4. In some examples, 埠130-1 through 130-4 may represent entities available for receiving/transmitting data (eg, in the form of data packets or frames) from I/O device 140. Connector or port. I/O device 140 is also shown to include a bore extender 144. According to some examples, as shown in FIG. 1, the ankle extender 144 can include E埠144-1C and E埠144-2D. For such examples, the 埠 extender 144 can enable the entity 埠 103-2 to extend to at least two extenders/logic 埠 to route data to the virtual switch 146 via the E 埠 144-1C and E 埠 144-2D and 147/ Routing data from virtual switchers 146 and 147.

In some examples, as shown in FIG. 1, I/O device 140 includes a switch manager 142. As described more below, the switch manager 142 can include logic and/or features to assign handover identification to data received at the I/O device 140. For such instances, the data may be received at the top of the various ports depicted in FIG. The assigned handover identification can then be used as part of the lookup table to determine one or more actions (eg, forwarding, cryptographic/security processing, etc.) for processing the data at I/O device 140.

According to some examples, I/O device 140 may be configured to be based on one It is recommended to operate at least some aspects of the IEEE standard (including descendants and variants) that have the title "Standard for Local and Metropolitan Area Networks-Virtual Bridged Local Area Networks-Bridge Port Extension". It is also identified as IEEE 802.1BR published on January 25, 2012 - Draft 3.2 (hereinafter "IEEE 802.1BR"). For such examples, I/O device 140 may also be configured to operate in accordance with at least some aspects of the proposed IEEE 802.1Qbg standard (including descendants and variants), or to implement at least some aspects. As part of the implementation of IEEE 802.1Qbg or IEEE 802.1BR, various data channels can be established for routing data locally between virtual machines on host device 101 or routing data across the network at network 160. element.

In some examples, as shown in FIG. 1, various established data channels are identified as data channels A through E. For these examples, the various VSIs coupled to VMs 111-116 are associated with data channels A, B, C, D, or E, except for VSI 118x coupled to virtual machine 118. In some examples, VSI 118x may represent a VSI that is still to be associated with an established data channel. As mentioned more below, the data routed via the VSI 118x may include control information to ultimately establish a data channel with the VSI 118x. For such executing individuals, a preset identification or tag for the control material may be generated or originated at the I/O device 140 and then used to assign the switching identification to the material.

According to some examples, a data channel can be used to route data between VMs located at host device 101, or to route data to VMs and located Between network elements at network 160. For such instances, the identification information for the data routed via such data channels may include the labels described by IEEE 802.1Qbg or IEEE 802.1BR. The tag can be a Service tag (S tag) or a Bridge Port Extension tag (E tag). In some examples, the S-tag or E-tag can be identification information to indicate that the material having one of the tags can be associated with a given channel. Such tags may be generated or originated globally from components at the remote end of I/O device 140, such as network elements at network 160.

In some examples, the switch manager 142 can include logic and/or features configured to receive data at the I/O device 140. The material may be associated with the VSI and may have identifying information (eg, an S-tag or an E-tag) to indicate association with channel A. As shown in FIG. 1, the VSI coupled to channel A or associated with channel A can be VSI 113A. For such instances, VSI 113A may be configured or configurable to couple to VM 113 and also configured to route data from VM 113 via virtual switch 143. According to some examples, since the data is routed via a data channel coupled to the network 160, the data can be considered to be received at the entity 埠 130-1 coupled to channel A. The handover manager 142 can include a switch identification number assigned or configured to assign a handover identification number based on an identifier assigned to the identifier 130-1, identification information for the data (eg, tag information), and at least a portion of the identification information. To the logic and / or characteristics of the data. The handover identification information can then be used as part of a lookup table by the logic and/or features of the handover manager 142 to determine one or more actions for processing the data at the I/O device 140.

In some other examples, there is identification information to indicate and channel The associated data of A can be received at I/O device 140 via 埠130-1. The data received via 埠 130-1 can then be routed to virtual switch 143 via channel A. As mentioned previously, the VSI 113A can be coupled to the VM 113. For such instances, the VSI 113A can be configured to send or transmit data to the VM 113. For such other examples, the switch manager 142 can include at least a portion configured or assembled to receive an identifier for the data (identification information and identification information for the data based on the identifier assigned to the I/O device 140. The originating end assigns the switching identification number to the logic and/or features of the material. The handover identification information can then be used as part of a lookup table by the logic and/or features of the handover manager 142 to determine one or more actions for processing the data at the I/O device 140.

In some examples, data may be received at a location included in I/O device 140, which may be routed between VM 111 and VM 112 via data channel D at virtual switch 141. The material received from VM 111 via LSI 14D at L埠 141-1D may have a destination for VM 112. For such instances, the identification information for the data received at 埠 141-1D may include a data channel identification number originating at I/O device 140 (eg, at virtual switch 141). The data channel D identification number can be similar to the format of the S tag or the E tag. The switch manager 142 can include an indication configured or assembled to be located at the I/O device 140 based on an identifier assigned to the identifier of the UI 141-1D, the channel-generated identification number generated by the region, and at least a portion of the identification information. Assign the switching identification number to the logic and/or characteristics of the material. The switching identification information can then be used as part of a lookup table by the logic and/or features of the switching manager 142 to determine that it is used in the I/O device. One or more actions are processed at 140.

In some examples, virtual switcher 141 can be configured to operate in accordance with IEEE 802.1Qbg and act as a virtual Ethernet bridge (VEB).

In some examples, communication links 150-1 through 150-4 can communicatively couple I/O device 140 to network 160 via ports 130-1 through 130-4, respectively. Communication links 150-1 through 150-4 may include various types of wired, wireless, or optical communication media. For such instances, communication links 150-1 through 150-4 can operate in accordance with one or more applicable communication or network connection standards in any version. Such communication or network connection standards may include, but are not limited to, IEEE 802.1Qbg or IEEE 802.1BR.

FIG. 2 illustrates an example switch identification structure 200. In some examples, handover manager 142 can include logic and/or features to use handover identification structure 200 to assign handover identification to data received at I/O device 140. As shown in FIG. 2, the handover identification structure includes fields 210, 220, and 230. In some examples, field 210 may indicate the origin of at least a portion of the identification information for the data. Field 220 may indicate an assigned 埠 identifier for use in receiving data at I/O device 140. Field 230 may indicate identifying information for the data. The identification information for the data may include a data channel identification number, such as an S-tag, an E-tag, or a preset information generated/originated by the region.

According to some examples, the originating end of the identification information may be indicated in the switching ID structure 200 by a 1-bit binary value of 0, and the global originating end may be indicated by a 1-bit value in the field 210. Again, the received 埠# in field 220 can be indicated by a 3-bit value. So, for example, The assigned identifier for "4" will be indicated by a 3-bit binary value of 100, and the assigned identifier of "2" will be indicated by a 3-bit binary value of 010. The invention is not limited to a 1-bit or 3-bit binary value for field 210 or 220, respectively.

In some examples, the identification information for the data included in field 230 may include a data channel identification number ranging from 1 to 4096. Also, the S-tag or E-tag information may include an identification number ranging from 1 to 4096. These identification numbers may be represented in field 230 as a 12-bit binary value or a 3-character hexadecimal value. The invention is not limited to a 12-bit binary value or a 3-character 16-digit value for field 230, or is not limited to a number ranging from 1 to 4096.

FIG. 3 illustrates an example assigned switch identification table 300. In some examples, the assigned switch ID table 300 depicts how the value associated with the switch ID structure 200 can be used to assign switch identification to the profile. For such instances, the assigned switch ID table 300 can be stored at least in memory (eg, memory 145) maintained at I/O device 140. The various virtual switches of I/O device 140 are listed in the left column of the assigned switch identification table 300, and the assigned handoff identifications for the received data are listed in the three columns on the right.

According to some examples, the switch manager 142 can include at least an assigned 埠 identifier based on the 用于 for receiving data, identification information (tag or preset value) for the data, and at least identification information. A portion of the source (region or global) assigns the switch identification to the logic and/or features of the profile. For example, the virtual switcher 141 is mentioned above as being generated Identification information for data routed between VM 111 and VM 112. Therefore, a value of 0 is indicated for the virtual switcher 141 in the "Region/Global" column. Also, in some examples, L埠141-1D of virtual switcher 141 may have been assigned a number of 1 and the number for virtual switch 141 is shown in table 300 as having 001 bis Carry value. In addition, the data can be transferred between the VSIs coupled to the virtual switch 141 via the data channel D. For this example, the data channel identification associated with data channel D can have a hexadecimal value of 0x005, and this value is shown in the "Identification Information" column in Figure 3.

In some examples, as mentioned above with respect to FIG. 1, virtual switchers 143 and 146-148 may be configured to receive data having identification information generated or originated at the far end of I/O device 140. Therefore, a value of 1 is indicated for the virtual switchers 143 and 146 to 148 in the "area/global" column. For such virtual switchers, the data received from the network 160 can be received via ports 130-1 through 130-3. These three turns can be assigned from 1 to 3 from left to right (see Figure 1), and these numbers are shown in table 300 as having binary values of 001, 010, and 011, respectively. In addition, data may be forwarded to or routed through VSIs coupled to such virtual switches via one of data channels A through E. According to some examples, the S-tag can be associated with data received via data channels A through E. The S-tags received via data channels A through E may have an identification number having hexadecimal values of 0x002, 0x003, 0x004, 0x005, and 0x006, respectively.

In some examples, virtual switch 149 can be assembled to pass via The data is received by being coupled to the unassigned data channel x of 埠130-4. Since the data channel does not have an assigned data number, the source of the identification information for the data received via channel x is considered to be the region, and a value of 1 is indicated for the virtual switch 149 to "area/global" In the column. As shown in FIG. 1 , the 埠 130-4 may be coupled to the fourth port of the network 160 . According to some examples, 埠130-4 may be assigned a number of 4 after having a carry value of 100, as indicated by the "Received 埠#" column. Also, the preset hexadecimal value indicated as 0x000 in the "Identification Information" column indicates that the data received at the virtual switch 149 may not yet be associated with the data channel identification number or assigned a data channel identification number.

According to some examples, as shown in the table 300, the data channel identification numbers of the data channel D at the virtual switch 141 and the data channel D at the virtual switch 147 are both 0x005. However, since the data channel identifier for the data channel D at the virtual switch 141 is from the regional origin, compared to the global identifier having a value of 1 for the data channel D at the virtual switch 147, The assigned handover identification is different due to the zone identifier having a value of zero.

FIG. 4 illustrates an example lookup table 400. As shown in FIG. 4, lookup table 400 includes fields for assigned handover identification, VSI identification, and associated actions. According to some examples, the assigned handover identification may have been based on the assigned handover ID table 300 as described above with respect to FIG. For these examples, the 1-bit and 3-bit binary values in the "Region/Whole Area" and "Received 埠#" fields can be combined to form a 4-bit binary value, and the 4-bit binary bit The value can then be converted to a 1-character hexadecimal value. 1 character hexadecimal value The third character can be added as a fourth character to the 3-character data characteristic value displayed in the "identification information" column of the assigned switching ID table 300. Due to these combinations, a given assigned handover identification may have a 4-character hexadecimal value as shown in lookup table 400. For example, a material having a global origin for identifying information and received at 埠3 of I/O device 140 will have a 4-bit binary value of 1011, and this value is converted to a hexadecimal value of B. Value (or a decimal value of 11).

According to some examples, as shown in FIG. 4, the lookup table 400 may include a "VSI Information" column to indicate identification information to include a virtual local area network (VLAN)/media access controller (MAC). ) ID. For such instances, the VLAN/MAC ID information along with the assigned handover ID can be used to further determine what actions will be taken for the data received at I/O device 140.

In some examples, as shown in FIG. 4, the received material can be assigned a 4-character switch identification number, and the switch manager 142 can include being configured or configured to use the assigned switch identification as part of the lookup table 400 and The VLAN/MAC ID information may be used to determine the logic and/or characteristics of the action for the material received via a given volume at I/O device 140.

According to some examples, the switch manager 142 maintained at the I/O device 140 can include logic and/or features to store the lookup table 400 at least temporarily at the memory 145. For such instances, at least portions of the memory 145 can be configured or assembled as a ternary content-addressable memory (TCAM). The data received at I/O device 140 and assigned to a given handoff identification can be quickly associated with each other The assigned handover identification is associated, and the corresponding processing action can be quickly determined using the assigned handover identification based on the content indicated in the lookup table 400.

In some examples, as shown for lookup table 400 in FIG. 4, the act of processing the data assigned to a given handoff identification may include routing the material directly to a given volume. For example, data having an assigned handover identification of 0x1 005 can be routed directly to the VSI 111D. This material can then be transmitted/transmitted from the VSI 111D to the VM 112.

According to some examples, as shown for lookup table 400 in FIG. 4, the acts for processing data assigned to a given handoff identification may include elements of I/O device 140 (eg, cryptographic processor circuitry) executing the data. The cryptographic compilation process then routes the material to the given 埠. For example, data having an assigned handover identification of 0x9002 can be forwarded to a cryptographic compilation processor circuit for encryption/decryption and then routed to VSI 113A. This material can then be transmitted/sent from the VSI 113A to the VM 113.

In some examples, as shown for lookup table 400 in FIG. 4, the actions for processing the data assigned to a given handoff identification may include elements (eg, security processor circuits) of I/O device 140 executing the data. The packet/frame check process is then routed to the given frame. For example, data having an assigned handover identification of 0xA005 can be forwarded to the security processor circuit for packet/frame verification and then routed to 埠143-1A. This material can then be transmitted/transmitted from the VSI 115D to the VM 115.

FIG. 5 illustrates a block for an example architecture of the switch manager 142. Figure. In some examples, the switch manager 142 includes features and/or logic that are configured or configured to assign handover identification to data received at an I/O device coupled to the host device. According to some examples, as shown in FIG. 5, the switch manager 142 includes switching logic 510, control logic 520, memory 530, and an input/output (I/O) interface 540. As illustrated in FIG. 5, the switching logic 510 can be coupled to the control logic 520, the memory 530, and the I/O interface 540. Switching logic 510 can include one or more of receiving feature 512, assigning feature 514, or looking up feature 516, or any reasonable combination thereof.

In some examples, the elements depicted in FIG. 5 are assembled to support or enable the switch manager 142 as described elsewhere herein. A given switching manager 142 may include some, all or more of the elements depicted in FIG. For example, switching logic 510 and control logic 520 can represent various logic devices or executable content separately or collectively to implement the features of switching manager 142. Example logic devices can include processor circuits, microprocessors, microcontrollers, processor circuits, field programmable gate arrays (FPGAs), special application integrated circuits (ASICs), multi-core/multi-threaded microprocessors One or more of the retreat thread or core, cryptographic compilation block, offload processor, or a combination thereof.

In some examples, as shown in FIG. 5, handover logic 510 includes a receive feature 512, an assignment feature 514, or a lookup feature 516. Switching logic 510 can be assembled to use one or more of these features to perform operations. For example, the receiving feature 512 can assist the I/O device in receiving data. The assignment feature 514 can be based on at least a portion of the assigned identifier for the data to be received at the I/O device, the identification information for the data, and the identification information. The originating end assigns a handover identification number. The lookup feature 516 can use the assigned switch identification as part of the lookup table to determine one or more actions for processing the data at the I/O device.

In some examples, control logic 520 can be configured to control the overall operation of switching manager 142. As mentioned above, control logic 520 can represent any of a wide variety of logic devices or executable content. For some examples, control logic 520 can be configured to operate in conjunction with executable content or instructions to implement control of switching manager 142. In some alternative examples, the features and functionality of control logic 520 may be implemented within switching logic 510.

According to some examples, memory 530 can be configured to store executable content or instructions for use by control logic 520 and/or switching logic 510. Executable content or instructions may be used to implement or initiate the features, elements or logic of the switch manager 142. As described more below, memory 530 can also be configured to at least temporarily maintain information associated with assigning a handover identification number to material received at an I/O device coupled to the host device.

Memory 530 can include a wide variety of non-volatile memory media including, but not limited to, one or more types of flash memory, programmable variables or states, read only memory (ROM), random access. Memory (RAM) or other static or dynamic storage media.

In some examples, I/O interface 540 can provide an interface between switching manager 142 and elements of an I/O device or elements of a host device via a regional communication medium or link. I/O interface 540 can include an interface that operates in accordance with various communication protocols or standards to communicate via regional communication media or links. Such communication protocols or standards may be described in one or more industry standards (including descendants and variants) such as industry standards associated with: Inter-Integrated Circuit (I ² C) specifications, System Management Bus (SMBus) Specification, Peripheral Component Interconnect Express (PCI Express) Specification, Universal Serial Bus (USB) Specification, or Serial Advanced Attachment Serial Advanced Technology Attachment (SATA) specification. However, the invention is not limited only to the above criteria and associated agreements.

According to some examples, the I/O interface 540 can be coupled to the I/O device at the switching manager 142 and the computing device coupled to the I/O device via a network communication link or channel. An interface is provided between the network elements associated with the communication link. I/O interface 540 can include an interface that operates in accordance with various communication protocols or standards to communicate via a network communication link or channel. Such communication protocols or standards may be described in Ethernet related standards or specifications (including descendants and variants) such as standards or specifications associated with IEEE 802.1Qbg or IEEE 802.1BR. The invention is not limited only to such Ethernet-related standards.

Figure 6 illustrates an example flow diagram for assigning handover identification. In some examples, elements of system 100 as shown in FIG. 1 may be used to illustrate example operations associated with the flowchart depicted in FIG. The switch manager 142 as shown in FIG. 1 or FIG. 5 can also be used to illustrate the example operations. However, the example operations described are not limited to implementation on system 100 or are not limited to switching manager 142 as described above with respect to FIG. 1 or FIG.

The switch ID structure 200, the assigned switch ID table 300, and the lookup table 400 as shown in FIG. 2 to FIG. 4 can also be used to illustrate and FIG. Example operations related to the flowchart. However, the example operations described are not limited to such specific structures or tables as shown in Figures 2 through 4.

From the beginning of the move to block 610 (receiving data), the switch manager 142 can include logic and/or features configured to assist the I/O device 140 in receiving data (e.g., via the receive feature 512). In some examples, the material may be in the form of a data packet or frame and have a destination associated with one or more virtual machines at host device 101 or with one or more network elements at network 160.

From block 610 to decision block 620 (from the network?), the switch manager 142 can include a configuration 130 to determine that the data is coupled to the communication links 150-1 through 150-4 via the 130-1 or 130 -4 or logic and/or features received (e.g., via receiving feature 512) at L埠141-1D included in virtual switcher 141. In some examples, the data may have been received from VM 111 or VM 112 by L埠 141-1D included in virtual switch 141. For these examples, the program moves to decision block 630. In other examples, the data may have been received from a network element located with or located at network 160. For these other examples, the program moves to decision block 650.

From decision block 620 to decision block 630 (with tags?), switch manager 142 can include identification information configured to determine whether the received material includes identification information such as an S-tag or an E-tag (eg, via assignment feature 514) Logic and / or features. In some instances, the data packet header associated with the data may not include identification information to identify associations with the data channel. For these examples, the program moves to block 640. Otherwise, if received The data includes identification information and the program moves to block 670.

From decision block 630 to block 640 (handover ID = {area, 埠 #, VSI channel ID}), handover manager 142 can include a switch configured to assign handover identification to the profile (eg, via assignment feature 514) Logic and / or features. In some instances, since the data does not include identification information, the source of the identification information will be the region.埠# will be the assigned identifier for the L埠141-1D included in the virtual switcher 141. The VSI channel ID may be the channel identification number assigned by the handover manager 142, which may be in a format similar to an S-tag or an E-tag.

From the decision block 620 to the decision block 650 (with tags?), similar to the decision block 630, the switch manager 142 can determine whether the received data includes identification information such as an S-tag or an E-tag. In some instances, the data packet header associated with the data may not include identification information to identify associations with the data channel. For these examples, the program moves to block 660. Otherwise, if the received data includes identification information, the program moves to block 670.

From decision block 650 to block 660 (handover ID = {area, 埠#, preset ID}), handover manager 142 can include a switch configured to assign handover identification to the profile (eg, via assignment feature 514) Logic and / or features. In some instances, similar to block 640, since the data does not include identification information, the source of the identification information will be the region. The 埠# may be an assigned identifier for 埠 (eg, 埠#4) coupled to one of the communication links 150-1 to 150-4 for receiving data from the network. The preset ID may be a preset channel identification number assigned by the switching manager 142, which may be similar to an S-tag or The format of the E tag.

From decision block 630 or decision block 650 to block 670 (handover ID = {global, 埠 #, tag}), handover manager 142 may include being configured to assign handover identification to the profile (eg, via assignment) The logic and/or features of feature 514). In some instances, the identification information for the data may have originated outside or far of the I/O device 140 and is therefore considered to be global. The 埠# may be an assigned identifier for 埠 (eg, 埠#2) coupled to one of the communication links 150-1 to 150-4 for receiving data from the network. Also, the tag may be identification information for the data and may be in a format similar to the S tag or the E tag.

Moving from block 640, 660 or 670 to block 680 (using a switch ID to process data), switch manager 142 may include logic and/or features to use the switch identification number assigned to the profile, and may also use VSI The ID information (VLAN/MAC ID) is used to determine one or more actions for processing data at the I/O device 140 (eg, via the lookup feature 516). In some examples, the action identified in the lookup table 400 for the corresponding switch identification number can be used to determine one or more actions for the profile. As mentioned above, the one or more actions may include routing data, cryptographic compilation of the data, or packet inspection processing of the data. The program then ends.

FIG. 7 illustrates an example system diagram for host device 700. As shown in FIG. 7, the host device 700 includes a hypervisor 705, an operating system 710, an application 720, a network input/output (I/O) device 730, a user input/output (I/O) device 740, and storage. The device 750, the memory 760, the central processing unit (CPU) 770, the chipset 780, and the communication (Comms) 790. According to some By way of example, several interfaces for interconnecting and/or communicatively coupling elements of host device 700 are also depicted in FIG. For example, user interface 715 and interface 735 may allow a user (not shown) and/or application 720 to be coupled to operating system 710 and/or hypervisor 705. Moreover, interface 735 may allow elements of supervisor 705 and/or operating system 710 (eg, device driver 711) to be communicatively coupled to elements of host device 700, such as network I/O device 730, user I /O device 740, storage 750, memory 760, CPU 770, chipset 780, or communication 790. For example, interface 754 can allow hardware and/or firmware elements of host device 700 to be communicatively coupled together, for example, via a system bus or other type of internal communication channel.

In some examples, as shown in FIG. 7, host device 700 can include an operating system 710. For example, operating system 710 can include one or more operating systems. The separate operating system included in operating system 710 can be implemented as part of a split virtual machine supported by components of host device 700. For such instances, the separate virtual machines can be associated with one or more processors included in CPU 770. Again, for these examples, hypervisor 705 can act as a virtual machine manager for such separate virtual machines.

According to some examples, as shown in FIG. 7, operating system 710 can include device driver 711 separately. Device driver 711 can include logic and/or features that are assembled to interact with (eg, via interface 735) hardware/firmware type elements of host device 700. For example, device driver 711 can include a device driver to control or direct storage 750 or memory 760 to fulfill requests made by application 720 or operating system 710. Device driver 711 can also include to allow network I/O device 730 to interact with CPU 770 and memory 760 to receive/deliver data via a communication channel coupled to host device 700 (eg, via network I/O device 730) Or the device driver of communication 790).

In some examples, application 720 can include an application that can be implemented on host device 700. For such instances, application 720 can request access (e.g., via operating system 710) or use of elements of a system such as user I/O device 740, storage 750, or memory 760.

According to some examples, network I/O device 730 can be similar to I/O device 140 described above with respect to FIG. For such examples, network I/O device 730 can include a switch manager 142 having logic and/or features that are configured or configured to assign handover identification to data received at network I/O device 730. (Not shown in Fig. 7). In some examples, network I/O device 730 can be configured to act as a network interface card (NIC).

In some examples, user I/O device 740 can include coupling One or more user input devices to interface 754 for entering data and commands to be executed by elements of host device 700. For example, the user input devices can include a keyboard, a mouse, a touch screen, a track pad, a trackball, an isopoint, a voice recognition system, and/or the like. Similarly, user I/O device 740 can include one or more user output devices coupled to interface 754 for outputting information to an operator or user. For example, such user output devices may include one or more displays, printers, speakers, and/or other output devices, as desired. For example, one of the user output devices can be a display. The display can be a cathode A cathode ray tube (CRT), a liquid crystal display (LCD), or any other type of display.

In some examples, storage 750 can include various types of memory that are assembled to be implemented or operated in a storage mode of operation. The storage 750 can include at least one of a combination of different types of storage devices or a combination thereof to store a relatively large amount of data. These different types of storage devices may include, but are not limited to, one or more of the following: a disk drive, a CD player, a tape drive, an internal storage device, an attached storage device, a flash memory, a battery Standby SDRAM (synchronous DRAM), network accessible storage, and/or other types of non-volatile memory (eg, phase change memory (PCM)). In some examples, the storage 750 can be included as part of the user I/O device 730 rather than a separate component as depicted in FIG.

According to some examples, memory 760 can include at least one or a combination of different types of memory to include RAM, DRAM, static RAM (SRAM), phase change material RAM (PRAM), and/or other types of volatile memory. . In some examples, memory 760 can be configured to maintain buffers used by network I/O device 730, components of CPU 770, and/or operating system 710 to at least temporarily store received data.

According to some examples, CPU 770 can be implemented as a central processing unit for host device 700. CPU 770 can include one or more processors having one or more processor cores separately. In some examples, CPU 770 can include any type of processor such as, for example, a multi-core processor, a reduced instruction set computer (RISC), a pipelined processor, a complex instruction set computer (complex) Instruction set computer, CISC), digital signal processor (DSP), and so on.

In some examples, chipset 780 can provide intercommunication between operating system 710, network user device 730, user I/O device 740, storage 750, memory 760, CPU 770, or communication 790. For example, the chipset 780 can provide intercommunication between the operating system 710, the user I/O device 740, the storage 750, and the CPU 770 to retrieve information from the storage 750 to display graphics for inclusion in the user I. On the display in the /O device 740. The graphics may have been presented by the CPU 770 upon request by the operating system included in the operating system 710.

In some examples, communication 790 can include logic and/or features to enable host device 700 to communicate externally with elements remotely from host device 700. Such logic and/or features may include communicating over a wired, wireless or optical communication channel or link via one or more wired, wireless or optical networks. In communications across such networks, communication 790 can operate in accordance with one or more applicable communication or network connection standards in any version. Also, in some examples, communication 790 can be integrated with network I/O device 730 to receive/retransmit data associated with communication to elements remotely of host device 700.

As mentioned above, the interface 754 can allow the hardware and/or firmware elements of the host device 700 to be communicatively coupled together. According to some examples, interface 754 can operate in accordance with one or more protocols or standards. Such agreements or standards may be described in one or more industry standards (including descendants and variants) such as industry standards associated with: inter-integrated circuit (I ² C) specifications, system management busses (SMBus) Specification, Accelerated Graphics Port (AGP) Specification, Fast Peripheral Component Interconnect (PCI Express) Specification, Universal Serial Bus (USB) Specification, High-Definition Multimedia Interface (High-Definition Multimedia Interface, HDMI) standards, digital visual interface (Digital visual interface, DVI) specification, Bluetooth ^TM specifications or serial advanced technology attachment (SATA) specification. However, the invention is not limited only to the above criteria and associated agreements.

In some examples, host device 700 can be included in a computing device. Examples of computing devices may include, but are not limited to, physical terminals, servers, blade servers, computing boards, workstations, desktops, personal computers (PCs) or laptops, hyper mobile computers, and the like.

One or more aspects of at least one example may be implemented by representative instructions stored on at least one machine readable medium representing various logic within a processor, the at least one machine readable medium being Or the system reads the logic that the machine, computing device or system makes to perform the techniques described herein. Such representations, referred to as "IP cores", may be stored on a tangible machine readable medium and supplied to various customers or manufacturing facilities for loading into a production machine that actually makes the logic or processor.

Various examples may be implemented using hardware components, software components, or a combination of the two. In some examples, hardware components can include devices, components, processors, microprocessors, circuits, circuit components (eg, transistors, resistors, capacitors, inductors, etc.), integrated circuits, special application products Body circuit (ASIC), programmable logic device (PLD), digital signal processor (DSP), field programmable gate array (FPGA), memory unit, logic gate, Registers, semiconductor devices, wafers, microchips, wafer sets, and the like. In some examples, software components may include software components, programs, applications, computer programs, system programs, machine programs, operating system software, intermediate software, firmware, software modules, routines, subroutines, functions, Method, program, software interface, application interface (API), instruction set, calculation code, computer code, code segment, computer code segment, word, value, symbol, or any combination thereof. As required for a given implementation, determining whether an instance is implemented using hardware components and/or software components can vary depending on any number of factors, such as: rate, power level, heat resistance, processing cycle budget , input data rate, output data rate, memory resources, data bus speed, and other design or performance constraints.

Some examples may include an article of manufacture or at least one computer readable medium. A computer readable medium can include a non-transitory storage medium to store logic. In some examples, the non-transitory storage medium can include one or more types of computer readable storage media capable of storing electronic data, including volatile or non-volatile memory, removable or non-removable memory. , erase or non-erase memory, writable or rewritable memory, and more. In some examples, the logic may include various software components, such as software components, programs, applications, computer programs, system programs, machine programs, operating system software, intermediate software, firmware, software modules, routines, times. A routine, a function, a method, a program, a software interface, an API, an instruction set, a computational code, a computer code, a code segment, a computer code segment, a word, a value, a symbol, or any combination thereof.

According to some examples, a computer readable medium can include a non-transitory The storage medium maintains or maintains instructions that, when executed by a machine, computing device or system, cause the machine, computing device or system to perform methods and/or operations in accordance with the described examples. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. The instructions may be implemented in accordance with a predefined computer language, manner, or grammar for instructing a machine, computing device, or system to perform a function. These instructions can be implemented using any suitable high-order, low-order, object-oriented, visual, compiled, and/or interpreted programming language.

Some examples may be described using the expression "in an instance" or "an instance" along with its derivatives. The terms "a" or "an" or "an" The appearances of the phrase "in an embodiment" are in

Some examples can be described using the expression "coupled" and "connected" along with their derivatives. These terms are not necessarily intended to be synonymous with each other. For example, the use of the terms "connected" and/or "coupled" may indicate that two or more elements are in direct physical or electrical contact with each other. However, the term "coupled" may also mean that two or more elements are not in direct contact with each other, but are still operating or interacting with each other.

It is emphasized that the Abstract of the Invention is provided to comply with Section 37.2(b) of 37 C.F.R., which requires an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. This abstract is submitted without an understanding of the scope or meaning of the scope of the patent application. In addition, before In the [Embodiment], it can be seen that various features are grouped together in a single instance for the purpose of simplifying the invention. The method of the present invention should not be construed as reflecting the intention that the claimed embodiments require more features than those specifically recited in the claims. As a matter of fact, the inventive subject matter lies in less than all features of a single disclosed example. Therefore, the scope of the following patent application is hereby incorporated by reference in its entirety in its entirety in its entirety in the the the the the the the the the In the context of the additional patent application, the terms "including" and "including" are used as the ordinary equivalents of the respective terms "including" and "including". In addition, the terms "first", "second", "third", etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

In some examples, a method can be implemented that includes receiving data at an input/output device coupled to one of the host devices. The data can be associated with a virtual station interface maintained at the input/output device. The virtual station interface can be communicatively coupled to a virtual machine implemented at the host device. The data may have been sent from one of the virtual machine or a network element that can be coupled to the input/output device via a network communication link. Assigning a handover identification based on an assigned identification code for receiving one of the data at the input/output device, identifying information for the data, and originating at least one of the identification information To the information. According to some examples, the assigned handover identification may be used as part of a lookup table to determine one or more actions for processing the data at the input/output device.

In some examples, implementation of the method can include receiving the capital The device includes one of: a physical port that can be coupled to the network communication link, or a logic port that can be coupled to a data channel that is configured to The data is routed from the virtual machine to another virtual machine implemented at the host device.

According to some examples, the implementation of the method may include: at least the source of the identification information is identified as an area based on the identification information for the data generated at the input/output device, or the source of the data The terminal is identified as a global domain based on the identification information for the data being generated outside the input/output device. For such instances, an area identification can be associated with a first identifier and a global identification can be associated with a second identifier. The assigned handover identification may include one of the first identifier or the second identifier based on whether the originator is identified as a region or a global region.

In some examples, implementation of the method can include the source of at least the portion of the identification information to be identified as a region. For such instances, the identification information for the data can include a data channel identification number associated with the virtual station interface communicatively coupled to the virtual machine.

According to some examples, implementation of the method can include the source of at least the portion of the identification information to be identified as a region. For such instances, the identification information for the data can include a predetermined identification number that is generated at the input/output device based on the data associated with the control data. The control profile can be related to establishing a data channel between the network element and the virtual machine. The data channel is routed via the virtual station interface.

In some examples, implementation of the method can include operating the input/output device in accordance with one or more Ethernet specifications. The one or more Ethernet specifications may include an IEEE 802.1Qbg Ethernet specification or an IEEE 802.1BR Ethernet specification. For such instances, the origin of at least the portion of the identification information can be identified as a global domain, and the identification number can include one of a service tag (S tag) or a bridge tag extension tag (E tag). The S-tag or the E-tag can be related to an established data channel between the network element and the virtual machine. The established data channel can be routed via the virtual station interface.

According to some examples, implementation of the method can include operating the I/O device in accordance with one or more Ethernet specifications. The one or more Ethernet specifications include an IEEE 802.1Qbg Ethernet specification or an IEEE 802.1BR Ethernet specification. For such instances, the origin of at least the portion of the identification information can be identified as an area, and the identification number will include one of a service tag (S tag) or a bridge extension tag (E tag). The S-tag or the E-tag can be related to an established data channel between the virtual machine and the network element. The established data channel can be routed via the virtual station interface.

In some examples, implementation of the method can include storing information associated with the plurality of switches of the I/O device in a single switch identification table maintained at the input/output device In a memory. The information can include the assigned handover identification for the data.

In some examples, implementation of the method can include using the assigned switch identification as part of a lookup table including the lookup table to be stored In one of the memories at the input/output device, the memory is configured as a ternary content addressable memory (TCAM).

In accordance with some embodiments, at least one machine-readable medium includes a plurality of instructions that, in response to execution on a computing device, cause the computing device to perform the example methods as mentioned above.

In some examples, an apparatus or apparatus can include components for performing the example methods as mentioned above.

According to some examples, an example apparatus or apparatus can include a processor circuit and a memory unit that is communicatively coupled to the processor circuit. The memory unit can be configured to store instructions for logic operable on the processor circuit. The logic can be configured to receive data at an input/output device that can be coupled to a host device. The data may have a destination associated with one of the virtual station interfaces maintained at the input/output device. The virtual station interface can be coupled to a virtual machine implemented at the host device. The data may have been sent from one of the virtual machine or a network element that can be coupled to the input/output device via a network communication link. The logic may also be configured to switch based on an assigned identifier for receiving the data at the input/output device, identification information for the data, and at least one of the source of the identification information Identify the assignment to this profile. For such instances, the logic can be configured to use the assigned switch identification as part of a lookup table to determine one or more actions for processing the data at the input/output device.

In some examples for the device of the example, the memory unit Volatile memory can be included.

In some examples for the example device, the UI for receiving the data can include one of: a physical entity that can be coupled to the network communication link; or a logical device The data channel can be coupled to a data channel configured to route data from the virtual machine to another virtual machine implemented at the host device.

According to some examples for the example device, the originator of at least the portion of the identification information can be identified as an area based on the identification information for the data being generated at the input/output device. The source of the data may also be identified as a global domain based on the identification information for the data being generated outside the input/output device. An area identification can be associated with a first identifier and a global identification can be associated with a second identifier. The assigned handover identification may include one of the first identifier or the second identifier based on whether the originator is identified as a region or a global region.

In some examples for the example device, the source of at least the portion of the identification information can be identified as a region. Moreover, the identification information for the data can include a data channel identification number associated with the virtual station interface that can be coupled to the virtual machine.

According to some examples for the example device, at least the source of the portion of the identification information can be identified as a region. For such instances, the identification information for the data can include a predetermined identification number that is generated at the input/output device based on the data associated with the control data. The control profile can be related to establishing a data channel between the network element and the virtual machine via the virtual station interface.

In some examples for the example device, the input/output device can be configured to operate in accordance with one or more Ethernet specifications, which will include a US electrical and electronic engineer Learn (IEEE) 802.1Qbg Ethernet specification or an IEEE 802.1BR Ethernet specification. For such instances, at least the source of the portion of the identification information can be identified as a global domain. The identification number can include one of a service tag (S tag) or a bridge tag extension tag (E tag). The S-tag or the E-tag can be related to an established data channel between the network element and the virtual machine. The data channel can be routed via the virtual station interface.

According to some examples for the example device, the input/output device can be configured to operate in accordance with one or more Ethernet specifications, which will include an American Society of Electrical and Electronics Engineers (IEEE) 802.1Qbg Ethernet Specification or an IEEE 802.1BR Ethernet Specification. For such instances, the origin of at least the portion of the identification information can be identified as an area, and the identification number will include one of a service tag (S tag) or a bridge extension tag (E tag). Moreover, the S-tag or the E-tag can be related to an established data channel between the virtual machine and the network element. The established data channel can be routed via the virtual station interface.

In some examples for the example device, the logic can also be configured to use the assigned switch identification as part of a lookup table stored in one of the memories at the input/output device. The memory can be configured as a ternary content addressable memory (TCAM).

Although in a language that is specific to structural features and/or method actions The subject matter is described, but it should be understood that the subject matter defined by the appended claims is not limited to the specific features or acts described. The specific features or acts described above are disclosed as examples of the scope of the patent application.

100‧‧‧ system

101‧‧‧ host device

103-2‧‧‧ Entity

111, 112, 113, 114, 115, 116, 117, 118‧‧‧ virtual machine (VM)

111D, 112D, 113A, 114B, 115C, 116D, 117E, 118x‧‧‧ Virtual Station Interface (VSI)

130-1, 130-2, 130-3, 130-4‧‧‧埠

140‧‧‧Input/Output (I/O) devices

141, 143, 146, 147, 148, 149‧‧ virtual switchers (V.S.)

141-D‧‧‧Logical (L埠)

142‧‧‧Switch Manager

143A/B, 146C, 147D, 148E, 149x‧‧ links

144‧‧‧埠 Extender

144-1C, 144-2D‧‧‧E埠

145‧‧‧ memory

150-1, 150-2, 150-3, 150-4‧‧‧ communication links

160‧‧‧Network

Claims (25)

A method comprising: receiving data at an input/output device coupled to a host device, the data being associated with a virtual station interface maintained at the input/output device, the virtual station interface being communicatively Coupled to a virtual machine implemented at the host device, the data is transmitted from the virtual machine or a network component, the network component being coupled to the network via a network communication link An input/output device; based on one of at least one of an assigned identifier of the UI for receiving the data at the input/output device, identification information for the data, and at least one of the identification information A handover identification is assigned to the profile; the assigned handover identification is used as part of a lookup table to determine one or more actions for processing the data at the input/output device. For example, in the method of claim 1, the receipt of the data includes one of: a physical entity capable of being coupled to the network communication link; or a coupling capable of being coupled to a data channel Logically, the data channel is configured to route data from the virtual machine to another virtual machine implemented at the host device. The method of any one of clause 1 or 2, wherein the source of the at least the portion of the identification information is identified based on the identification information for the data generated at the input/output device District The domain, or the source of the data, is identified as a global domain based on the identification information for the data generated external to the input/output device, a region identification system associated with a first identifier and a global identification system A second identifier is associated, the assigned handover identification comprising one of the first identifier or the second identifier based on whether the originator is identified as a region or a global region. The method of any one of the items 1 to 3, wherein the source of the at least the portion of the identification information is identified as an area, and the identification information for the data includes a data channel identification number. The data channel identification number is associated with the virtual station interface communicatively coupled to the virtual machine. The method of any one of the items 1 to 3, wherein the source of the identification information is identified as an area, and the identification information for the data includes a preset identification number. The preset identification number is generated at the input/output device based on the data associated with the control data, and the control data is related to establishing a data channel between the network component and the virtual machine, the data channel system Routed via the virtual station interface. The method of any one of claims 1 to 3, comprising operating the input/output device in accordance with one or more Ethernet specifications, the one or more Ethernet specifications including The Institute of Electrical and Electronics Engineers (IEEE) 802.1Qbg Ethernet specification or an IEEE 802.1BR Ethernet specification, the originator of at least the portion of the identification information is identified as a global domain, and the identification number includes a service tag (S Label) or one of the bridge extension labels (E labels). The method of claim 6, wherein the S-tag or the E-tag is an established data channel between the network element and the virtual machine, and the established data channel is routed through the virtual station interface. . The method of any one of claims 1 to 3, comprising operating the I/O device in accordance with one or more Ethernet specifications, the one or more Ethernet specifications including The Institute of Electrical and Electronics Engineers (IEEE) 802.1Qbg Ethernet specification or an IEEE 802.1BR Ethernet specification, at least the portion of the identification information identified as an area, and the identification number will include a service One of the label (S label) or a bridge extension label (E label). The method of claim 8, wherein the S tag or the E tag is an established data channel between the virtual machine and the network element, and the established data channel is routed through the virtual station interface. . The method of any one of clauses 1 to 9, wherein the information associated with the plurality of switches of the I/O device is stored in a single handover identification table, the single handover identification table being maintained In one of the memory at the input/output device. A method of claim 10, comprising: the information comprising the assigned handover identification for the material. The method of any one of clauses 1 to 11, wherein the assigned switching identification is included as part of a lookup table, and the lookup table is stored in a memory at the input/output device, The memory is configured as a ternary addressable content memory (TCAM). At least one machine-readable medium comprising a plurality of instructions responsive to execution on a computing device to cause the computing device to perform the method of any one of claims 1 to 12. An apparatus comprising means for performing the method of any one of clauses 1 to 13 of the patent application. An apparatus comprising: a processor circuit; and a memory unit communicatively coupled to the processor circuit, the memory unit configured to store instructions for logic operable on the processor circuit, The logic is configured to receive data at an input/output device capable of being coupled to a host device having a destination associated with a virtual station interface maintained at the input/output device, the virtual The station interface can be coupled to a virtual machine implemented at the host device, the data being transmitted from one of the virtual machine or a network element, the network element being capable of being coupled via a network communication link Connected to the input/output device, the logic is also configured to assign an identifier based on one of the identifiers used to receive the data at the input/output device, identification information for the data, and Identifying at least one of the source of information, and assigning a handover identification to the profile, the logic being configured to use the assigned handover identification as part of a lookup table for determining One or more actions of the data are processed at the input/output device. The device of claim 15, comprising: the memory unit comprising volatile memory. The apparatus for receiving the data includes one of the following: a physical entity capable of being coupled to the network communication link; or capable of being coupled, as claimed in any one of claims 15 or 16 A logical port to a data channel configured to route data from the virtual machine to another virtual machine implemented at the host device. The apparatus of any one of clauses 15 to 17, wherein the source of the at least the portion of the identification information is identified based on the identification information for the data generated at the input/output device For the region, or the source of the data is identified as a global domain based on the identification information for the data generated outside of the input/output device, a region identification system associated with a first identifier and a global identification system Associated with a second identifier, the assigned handover identification will include one of the first identifier or the second identifier based on whether the originator is identified as a region or a global region. The device of claim 18, wherein the source of at least the portion of the identification information is to be identified as an area, and the identification information for the data includes a data channel identification number, the data channel The identification number is associated with the virtual station interface that can be coupled to the virtual machine. The device of claim 18, wherein the source of at least the portion of the identification information is to be identified as an area, and the identification information for the data includes a preset identification number, the preset The identification number is generated at the input/output device based on the data associated with the control material, the control data being related to the virtual component and the virtual A data channel is established between the machines, and the data channel is routed through the virtual station interface. The device of any one of clauses 15 to 18, wherein the input/output device is configured to operate in accordance with one or more Ethernet specifications, the one or more Ethernet specifications Including an American Institute of Electrical and Electronics Engineers (IEEE) 802.1Qbg Ethernet specification or an IEEE 802.1BR Ethernet specification, at least the portion of the identification information of the source will be identified as a global domain, and the identification number will Includes one of a service tag (S tag) or a bridge tag extension tag (E tag). In the device of claim 21, the S-tag or the E-tag is an established data channel between the network element and the virtual machine, and the data channel is routed through the virtual station interface. The device of any one of clauses 15 to 18, wherein the input/output device is configured to operate in accordance with one or more Ethernet specifications, the one or more Ethernet specifications Including an American Institute of Electrical and Electronics Engineers (IEEE) 802.1Qbg Ethernet specification or an IEEE 802.1BR Ethernet specification, at least the part of the identification information of the identification information will be identified as an area, and the identification number will Includes one of a service tag (S tag) or a bridge tag extension tag (E tag). For example, in the device of claim 23, the S tag or the E tag is an established data channel between the virtual machine and the network component, and the established data channel is routed through the virtual station interface. by. The apparatus of any one of clauses 15 to 24, comprising: the logic is also configured to use the assigned switching identification as being stored in a memory of the input/output device A portion of a lookup table that is configured as a ternary addressable content memory (TCAM).