WO2018094743A1

WO2018094743A1 - Method for processing packet, and computer device

Info

Publication number: WO2018094743A1
Application number: PCT/CN2016/107521
Authority: WO
Inventors: 张丰伟; 徐君; 戴芬; 王元钢
Original assignee: 华为技术有限公司
Priority date: 2016-11-28
Filing date: 2016-11-28
Publication date: 2018-05-31
Also published as: CN108377671B; CN108377671A

Abstract

Disclosed in an embodiment of the present invention are a method for processing a packet, and a computer device. The method comprises: acquiring a first processor core identifier to which a service is bound; determining, according to the first processor core identifier and configured mapping relationship information, a first local port number corresponding to the service, wherein the mapping relationship information comprises a mapping relationship between the processor core identifier and the port number; writing the first local port number to a source port number segment in a packet of the service to be transmitted; and transmitting the packet to be transmitted to a transmit queue of a network card. The method for processing a packet and the computer device disclosed in the embodiment of the present invention can increase packet forwarding efficiency.

Description

Method and computer device for processing messages

Technical field

The present invention relates to the field of information technology and, more particularly, to a method and computer apparatus for processing a message.

Background technique

Now that the NIC is moving toward intelligence, it has provided routing functions based on the specified field in the message network header, and has brought significant performance improvements.

When the NIC is initialized, it specifies the number of queues used by the NIC and gives each queue an index. When the NIC receives the packet, it forwards the packet to the queue of the specified index according to the forwarding flow table. The field field of the general forwarding flow table includes the source Internet Protocol (IP) and destination IP, the source port number and the destination port number, and the mask and matching fields, and the action field after the hit. For example, the Action can be: "Direct to queue i", where i is the index of the queue queue.

When the client and server send a packet, the port number used can be any port number in the port range (for example, 0-65535). However, due to media and power consumption, the number of entries in the forwarding flow table is much smaller than the number of port numbers. Therefore, if any port number is used, the NIC may not be able to match the corresponding entry when forwarding the packet to the receiving queue, which may affect the forwarding efficiency of the packet.

Summary of the invention

The embodiment of the invention provides a method and a computer device for processing a message, which can improve the forwarding efficiency of the message.

In a first aspect, a method for processing a message is provided, including:

Obtaining a first processor core identifier of the service binding;

Determining, according to the first processor core identifier, and the configured mapping relationship information, a first local port number corresponding to the service, where the mapping relationship information includes a mapping relationship between the processor core identifier and the port number;

Writing the first local port number to the source port number field of the to-be-sent packet of the service;

Send the to-be-sent message to the network card sending queue.

A method for processing a message according to an embodiment of the present invention, by binding a service to a processor core identifier, and The port number corresponding to the service is determined according to the port number, and the to-be-sent packet of the service is processed according to the port number, so that the network card can forward the to-be-received packet of the service to the corresponding network card queue according to the port number, thereby improving the packet. Forwarding efficiency.

In some possible implementation manners, the mapping relationship information includes a mapping relationship between a processor core identifier, a network card receiving queue, and a port number.

In some possible implementation manners, the mapping relationship between the processor core identifier, the network card receiving queue, and the port number may be a mapping relationship between the processor core identifier and the network card receiving queue, and a mapping relationship between the network card receiving queue and the port number.

In some possible implementations, each processor core identifier corresponds to a plurality of port numbers.

In some possible implementations, one processor core identifier may correspond to multiple network card queues, and one network card queue may correspond to multiple port numbers.

In some possible implementations, determining the first local port number includes:

The first local port number is selected from a plurality of port numbers corresponding to the first processor core identifier.

In some possible implementations, the method further includes:

Configure the mapping relationship information.

In some possible implementations, the method further includes:

Obtaining a to-be-received packet of the service from the network card receiving queue corresponding to the first local port number, wherein the to-be-received packet is forwarded by the network card to the first local port number according to the destination port number in the to-be-received packet The corresponding network card receiving queue.

In some possible implementation manners, the to-be-sent message includes a link request message of the client;

Before the obtaining the first processor core identifier of the service binding, the method further includes:

Binding the service to the first processor core identity.

By binding the service to the processor core identifier, the processor core corresponding to the service can be known in advance, so that both the service and the protocol stack can be mapped to the same processor core, thereby improving the processing efficiency of the service packet.

In some possible implementation manners, the to-be-sent message includes a server-side link accepting message;

Binding the service to the first processor core identifier according to the listening port number of the service and the mapping relationship information;

Obtaining a link request message of the service from the network card receiving queue corresponding to the listening port number.

In some possible implementation manners, the network card may forward the packet to the specified network card queue according to the forwarding flow table.

In some possible implementation manners, the forwarding flow table may be generated according to the mapping relationship information.

In some possible implementation manners, the network card may forward the to-be-received packet of the service to the corresponding receiving queue according to the first local port number, so that the packet can be effectively forwarded.

In some possible implementations, the port number includes a TCP or UDP port number.

In a second aspect, a method for processing a message is provided, including:

Binding the service to the first processor core identifier according to the listening port number of the service and the configured mapping relationship information, where the mapping relationship information includes a mapping relationship between the processor core identifier and the port number;

Obtaining a to-be-received message of the service from the first network card receiving queue, where the first network card receiving queue is a network card receiving queue corresponding to the first processor core identifier.

The method for processing a message in the embodiment of the present invention, by binding the service to the processor core identifier, can enable the network card to forward the packet to the corresponding network card queue, thereby improving the forwarding efficiency of the packet, and on the other hand, Both the service and the protocol stack correspond to the same processor core, thereby improving the processing efficiency of the service packets.

In some possible implementations, the method further includes:

Writing the listening port number to the source port number field of the to-be-sent packet of the service;

Send the to-be-sent message to the network card sending queue.

In some possible implementations, the listening port number is a UDP port number.

In a third aspect, a host is provided, comprising a module that performs the method of the first aspect or any possible implementation of the first aspect, or the method of any of the possible implementations of the second aspect or the second aspect Module.

In a fourth aspect, a host is provided, the host including a processor and a memory, the memory is for storing an instruction, the processor is configured to execute the instruction, and when the processor executes the instruction stored by the memory, the executing causes the processor Performing the first aspect or any possible implementation of the first aspect, or the method of the second aspect or any possible implementation of the second aspect.

In a fifth aspect, a computer device is provided, including:

a host, configured to obtain a first processor core identifier of the service binding, and determine, according to the first processor core identifier and the configured mapping relationship information, a first local port number corresponding to the service, where the mapping relationship information includes The mapping between the processor core identifier and the port number, the first local port number is written in the source port number field of the to-be-sent packet of the service, and the to-be-sent packet is sent to the network card sending queue;

The network card is configured to send the to-be-sent packet in the sending queue of the network card.

The computer device of the embodiment of the present invention binds the service to the processor core identifier, and determines the port number corresponding to the service according to the port number, and processes the to-be-sent packet of the service according to the port number, so that the network card can be made according to the port number. The packets to be received of the service are forwarded to the corresponding network card queue, so that the forwarding efficiency of the packets can be improved.

In some possible implementations, the host is specifically configured to select the first local port number from the plurality of port numbers corresponding to the first processor core identifier.

In some possible implementations, the host is further configured to configure the mapping relationship information.

In some possible implementations, the network card is further configured to receive a to-be-received packet of the service, where the destination port number in the to-be-received packet is the first local port number, and the to-be-received according to the destination port number. The packet is forwarded to the network card receiving queue corresponding to the first local port number;

The host is further configured to obtain the to-be-received packet from the network card receiving queue corresponding to the first local port number.

In some possible implementations, the computer device is a client device, and the to-be-sent message includes a link request message;

The host is further configured to bind the service to the first processor core identity.

In some possible implementations, the computer device is a server, and the to-be-sent message includes a link accept message;

The host is further configured to bind the service to the first processor core identifier according to the listening port number of the service and the mapping relationship information;

The network card is further configured to receive a link request message of the service, where the destination port number in the link request message is the listening port number, and forward the to-be-received message to the corresponding listening port number according to the destination port number. NIC receiving queue;

The host is further configured to obtain the link request message from the network card receiving queue corresponding to the listening port number.

In a sixth aspect, a computer device is provided, comprising:

The host is configured to bind the service to the first processor core identifier according to the listening port number of the service and the configured mapping relationship information, where the mapping relationship information includes a mapping relationship between the processor core identifier and the port number, The first network card receiving queue obtains the to-be-received message of the service, where the first network card receiving queue is the network card receiving queue corresponding to the first processor core identifier;

The network card is configured to receive the to-be-received packet, and the destination port number in the to-be-received packet is the listening port number, and the to-be-received packet is forwarded to the first network card receiving queue according to the destination port number.

The computer device of the embodiment of the present invention, by binding the service to the processor core identifier, can enable the network card to forward the packet to the corresponding network card queue, thereby improving the forwarding efficiency of the packet, and on the other hand, the service and the protocol can be implemented. The stacks all correspond to the same processor core, thereby improving the processing efficiency of the service packets.

In some possible implementation manners, the host is further configured to: write the listening port number into a source port number field of the to-be-sent packet of the service, and send the to-be-sent packet to the network card sending queue;

The network card is further configured to send the to-be-sent packet in the network card sending queue.

In some possible implementations, the computer device is a server.

In a seventh aspect, a computer apparatus is provided, comprising the host of the third aspect or the fourth aspect, and a network card.

In an eighth aspect, a computer readable medium is provided for storing a computer program, the computer program comprising any of the possible implementations of the first aspect or the first aspect, or the second or second aspect The instructions of the method in any of the possible implementations.

DRAWINGS

FIG. 1 is a schematic diagram of a computer device to which the technical solution of the embodiment of the present invention is applied.

2 is a schematic diagram of a mapping relationship between a processor core identifier, a network card queue, and a port number according to an embodiment of the present invention.

FIG. 3 is a schematic flowchart of a method for processing a message according to an embodiment of the present invention.

FIG. 4 is a schematic flowchart of a method for processing a message according to another embodiment of the present invention.

FIG. 5 is a schematic flowchart of a method for processing a message according to still another embodiment of the present invention.

FIG. 6 is a schematic flowchart of a method for processing a message according to still another embodiment of the present invention.

FIG. 7 is a schematic flowchart of a method for processing a message according to still another embodiment of the present invention.

FIG. 8 is a schematic flowchart of a method for processing a message according to still another embodiment of the present invention.

9 is a schematic block diagram of a computer device in accordance with an embodiment of the present invention.

detailed description

As shown in FIG. 1, computer device 100 can include a processor 111, a memory 112, and a network card 120.

Processor 111 and memory 112 may in turn be collectively referred to as host 110. Host 110 (e.g., an application in host 110) can send messages to other devices via network card 120.

Processor 111 can include multiple processor cores (Cores). Memory 112 can include memory and other memory.

The network card 120 supports multiple network card queues, which may also be referred to as queues. The queue includes a send queue and a receive queue. The queue of network card 120 can be configured in memory 112, such as in memory. The network card 120 can obtain the message to be sent from the sending queue or forward the message received by the network card to the receiving queue based on the address of the queue.

In some possible implementation manners, the network card 120 may forward the packet to the designated network card queue according to the destination IP and the mask and the matching domain of the packet in the packet network header.

In some possible implementations, the network card 120 can forward the message to the designated network card queue according to the forwarding flow table. The forwarding flow table may be configured in the network card 120 or in a memory accessible by the network card 120.

In some possible implementations, a mapping relationship is configured between a processor core identifier (CoreID), a network card queue, and a port number. The forwarding flow table can be generated according to the mapping relationship.

FIG. 2 shows a schematic diagram of a mapping relationship between a processor core identifier, a network card queue, and a port number.

As shown in FIG. 2, since the number of port numbers is relatively large, each network card queue and processor core identifier correspond to multiple port numbers. These multiple port numbers can also be referred to as NIC queues or port resource pools identified by the processor core.

It should be understood that the correspondence between the network card queue and the processor core identifier may be one-to-one or not one-to-one, which is not limited by the embodiment of the present invention.

It should also be understood that the embodiment of the present invention maps the processor core identifier, the network card queue, and the port number. The specific form of the system is not limited. It can be expressed as a mapping relationship between the three, or a mapping relationship between the two. For example, the mapping between the processor core identifier and the NIC queue can be performed. And the mapping relationship between the NIC queue and the port number.

In the embodiment of the present invention, on the basis of the foregoing mapping relationship, the service is bound to the CoreID, so that the port number corresponding to the service can be determined according to the binding relationship. The port number determined in this way can be matched to a specific network card queue, so that the network card can forward packets, which can improve the forwarding efficiency of packets.

It should be understood that the service in the embodiment of the present invention may be a Transmission Control Protocol (TCP)/User Data Protocol (UDP) service, and the port number may be a TCP/UDP port number, but the present invention is implemented. This example is not limited to this.

FIG. 3 is a schematic flowchart of a method 300 for processing a message according to an embodiment of the present invention. The method 300 can be performed by a host. The host can be a host in the client device or a host in the server. For the client, the to-be-sent message of the service may be a link request message and a data message after the link is established; for the server, the service-to-send message may be a link-received message and a link-established data message. The link request message may be a message sent by the client to the server for requesting to establish a communication connection with the server. The connection accepting message may be a message sent by the server to the client for establishing a communication connection with the client.

310: Obtain a first processor core identifier of the service binding.

In the embodiment of the invention, the service is bound to the CoreID. In this way, the subsequent port number of the service can be determined according to the bound CoreID, and then the packet of the service is processed.

Optionally, for the client, the service can be bound to the CoreID before the link class socket (Socket) associated with the service is created; for the server, before or after the listener socket associated with the service is created This service is bundled with CoreID.

320. Determine, according to the first processor core identifier, a first local port number corresponding to the service.

According to the first processor core identifier of the service binding, the local port number corresponding to the service (represented as the first local port number) may be selected. The first local port number is also the port number of the Socket associated with the service, that is, subsequent packets of the Socket can be transmitted according to the first local port number.

Optionally, in an embodiment of the present invention, the first local port number may be determined according to the first processor core identifier and the configured mapping relationship information.

The port number corresponding to the first processor core identifier may be selected as the first local port number according to the configured mapping relationship information.

Optionally, the mapping relationship information may be pre-configured in a memory. The mapping relationship information can be obtained by an application in the host.

Optionally, the mapping relationship information may include a mapping relationship between the processor core identifier and the port number.

Optionally, the mapping relationship information may include a mapping relationship between the processor core identifier, the network card receiving queue, and the port number.

Optionally, the mapping relationship information may include a mapping relationship between the processor core identifier and the network card receiving queue, and a mapping relationship between the network card receiving queue and the port number.

Optionally, each processor core identifier can correspond to multiple port numbers.

For example, the mapping relationship information may include a mapping relationship as shown in FIG. 2.

It should be understood that the embodiment of the present invention does not limit the specific form and content of the mapping relationship information, that is, the mapping relationship information may also adopt other mapping relationships.

Optionally, in a case that each processor core identifier corresponds to multiple port numbers, the first local port number may be selected from multiple port numbers corresponding to the first processor core identifier.

330. Process the to-be-sent packet of the service according to the first local port number.

The first local port number is the source port number of the to-be-sent packet of the service, and is the destination port number of the to-be-received packet of the service.

Specifically, when the to-be-sent packet is sent, the host may write the first local port number to the source port number field of the to-be-sent packet, and send the to-be-sent packet to the network card sending queue. The network card sends the to-be-sent packet in the NIC sending queue.

Optionally, the host may obtain the to-be-received packet of the service from the network card receiving queue corresponding to the first local port number, where the to-be-received packet is determined by the network card. The destination port number in the to-be-received packet is forwarded to the network card receiving queue corresponding to the first local port number.

Specifically, the source port number of the to-be-sent packet of the service is the first local port number, and correspondingly, the destination port number in the to-be-received packet of the service is the first local port number. In this way, the network card can forward the to-be-received packet to the network card receiving queue corresponding to the first local port number according to the destination port number in the to-be-received packet, and the host can receive the queue from the network card corresponding to the first local port number. Obtain the pending message of the service.

Optionally, the forwarding flow table of the network card may be configured based on the mapping relationship information described above. For example, multiple port numbers correspond to one NIC queue. Based on the range of the port number, you can calculate the mask and matching field of the forwarding flow table entry. For example, if a port number range is: 1024-2047; then the segmentation The mask is: 0100-0000-0000(1024)->0111-1111-1111 (2047). Therefore, the matching field of the corresponding forwarding flow table entry can be calculated as 0100-0000-0000, and the mask is 0111-1111-1111.

Optionally, the all-matching entry may also be set. When all the entries in the forwarding flow table do not match, the entry is finally matched.

The method for processing a message according to the embodiment of the present invention is to bind the service to the processor core identifier, and determine the port number corresponding to the service according to the port number, and process the to-be-sent packet of the service according to the port number, so that the network card can be The port number forwards the to-be-received packet of the service to the corresponding network card queue, thereby improving the forwarding efficiency of the packet.

The processing flow of the client and server is described in detail below.

Optionally, in an embodiment of the present invention, for the client, the to-be-sent message includes a link request message of the client.

In this case, as shown in FIG. 4, before step 310, the method 300 may further include:

302. Bind the service to the first processor core identifier.

Specifically, when the client needs to link the service, to create a link class socket associated with the service, you need to select a port number. In an embodiment of the invention, the service is bound to a CoreID, ie, the service is bound to the processor core (Core) of the process running the service. On the client side, there is no limit on the choice of the Core, that is, the Core can be randomly selected. Then, the local port number corresponding to the service, that is, the Socket port number, may be determined according to the CoreID of the service binding, and then the link request message is transmitted according to the local port number corresponding to the service.

The following describes the processing flow of the client from the perspective of the software module. It should be understood that the flow of the software module is a logical process, and the process may be performed by a processor in the host, and the description from the perspective of the software module is only for facilitating understanding of the technical solution of the embodiment of the present invention.

FIG. 5 is a schematic diagram of a processing flow of a client shown from the perspective of a software module.

501, the application creates a link class Socket.

An app can also be called an app. The application in the client needs to create a link class Socket when it needs to obtain the service, that is, it needs to communicate with the application in the server. For example, the application calls the application programming interface (API) provided by the operating system to create a TCP-linked Socket.

502. The TCP/UDP protocol stack module determines whether the service is bound to the Core.

The TCP/UDP protocol stack module is a module for processing TCP/UDP protocol stacks. It should be understood that since the application, the application's process, or the thread all correspond to the service, the service and Core binding may also be an application, an application's process, or a thread bound to the Core. For example, the TCP/UDP protocol stack module queries the CoreID of the service binding through an API provided by the operating system. If the corresponding CoreID is queried, step 505 is performed, otherwise step 503 is performed.

503. The TCP/UDP protocol stack module feeds back to the application and needs to bind the Core.

For example, the TCP/UDP protocol stack module needs to bind a Core by feeding back error information to the application.

504, the application binds the service to a Core.

505. The TCP/UDP protocol stack module notifies the Flow-Director management module to obtain the port number.

In the embodiment of the present invention, the flow-director management module may be configured to configure a network card queue, mapping relationship information, and the like.

For example, the TCP/UDP protocol stack module informs the Flow-Director management module of the CoreID of the service module binding, and notifies the Flow-Director management module to obtain the Socket port number, that is, the port number corresponding to the service.

506. The Flow-Director management module acquires a port number according to the bound CoreID and the mapping relationship information.

For example, the Flow-Director management module obtains the Socket port number according to the binding CoreID and the mapping relationship between the preset CoreID, the NIC queue, and the port number.

507. The TCP/UDP protocol stack module processes the link request message according to the port number.

For example, the TCP/UDP protocol stack module writes the port number to the source port number field of the link request message, and sends the link request message to the network card send queue.

When the subsequent server sends the packet of the service, the port number is used as the destination port number, so that the NIC of the client can forward the packet to the corresponding receiving queue according to the destination port number, so that the packet can be effectively forwarded. .

Optionally, in another embodiment of the present invention, for the server, the to-be-sent message includes a server-side link accept message.

In this case, as shown in FIG. 6, before step 310, the method 300 may further include:

304. Bind the service to the first processor core identifier according to the listening port number of the service.

305. Obtain a link request report of the service from a network card receiving queue corresponding to the listening port number. Text.

Specifically, when the server side listens for the link request, it needs to create a listener class Socket associated with the service, where the listening port number is a port number known by the client. That is, the listening port number is the destination port number when the client sends the link request message. The server binds the service to the CoreID according to the listening port number. For example, the service is bound to the CoreID according to the listening port number and the configured mapping relationship information.

In addition, according to the listening port number, the server can also know the network card receiving queue corresponding to the link request message. When receiving the link request message of the client, the network card of the server side forwards the link request message to the corresponding network card receiving queue according to the destination port number in the link request message, that is, the listening port number. The host on the server side can obtain the link request message from the network card receiving queue corresponding to the listening port number.

After obtaining the link request message and accepting the link request, the server end sends a link acceptance message and a data message to the client. At this time, the server side needs to determine the next transmission port number, that is, the first local port number described above. The server may determine the first local port number according to the CoreID bound to the service, and then transmit the link acceptance message and the subsequent data packet according to the first local port number.

Fig. 7 is a schematic diagram showing the processing flow of the server side from the perspective of a software module.

701, the application creates a listener class Socket.

The application calls the API provided by the operating system to create a listener class Socket.

702. The TCP/UDP protocol stack module obtains a CoreID that the service should be bound to the Flow-Director management module.

The TCP/UDP protocol stack module passes the listening port number to the Flow-Director management module to obtain the CoreID that the service should bind.

703. The Flow-Director management module acquires a corresponding CoreID according to the listening port number.

For example, the Flow-Director management module obtains the corresponding CoreID according to the listening port number and the preset mapping relationship information, that is, the CoreID to which the service should be bound, and feeds back to the TCP/UDP protocol stack module.

704. The TCP/UDP protocol stack module determines whether the service is bound to the Core.

For example, the TCP/UDP protocol stack module queries whether the CoreID of the service binding is empty (no binding) through the API provided by the operating system. If it is empty, execute 705, otherwise execute 706.

705. The TCP/UDP protocol stack module binds the service to the Core fed back by the Flow-Director management module.

706. The TCP/UDP protocol stack module feeds back the CoreID that should be bound to the application.

The application binds or exits the current process.

707. The TCP/UDP protocol stack module notifies the Flow-director management module to obtain a data transmission port number.

When a client actively links to the server, and the server accepts the link request, the TCP/UDP protocol stack module notifies the FlowID of the Flow-director management module service binding to obtain the data transmission port number.

708. The flow-director management module returns a port number corresponding to the CoreID according to the bound CoreID and the preset mapping relationship information.

709. The TCP/UDP protocol stack module processes the packet of the service according to the port number.

The TCP/UDP protocol stack module processes the link acceptance message and the subsequent data message according to the port number. For example, the TCP/UDP protocol stack module writes the port number to the source port number field of the message and sends the message to the network card send queue.

When the subsequent client sends the packet of the service to the server, the port number is used as the destination port number, so that the network card of the server can forward the packet to the corresponding receiving queue according to the destination port number, so that the packet can be reported. The effective forwarding of the text.

It should be understood that on the server side, for example, for the UDP protocol, the transmission port number, that is, the first local port number described above, may be no longer selected, but the listening port number is always used. This case will be described below.

FIG. 8 is a schematic flowchart of a method 800 for processing a message according to another embodiment of the present invention. The method 800 can be performed by a host. This host can be a host in the server.

810. Bind the service to the first processor core identifier according to the listening port number of the service.

The listening port number is the port number known to the client. The server can bind the service to the CoreID according to the listening port number.

Optionally, the service may be bound to the first processor core identifier according to the listening port number and the configured mapping relationship information. For the description of the mapping relationship information, refer to the foregoing embodiment, and for brevity, no further details are provided herein.

820. Obtain a to-be-received packet of the service from the first network card receiving queue, where the first network card receiving queue is a network card receiving queue corresponding to the first processor core identifier.

After the service is bound to the processor core identifier, the server can obtain the to-be-received packet of the service, that is, the network card receiving queue corresponding to the request packet sent by the client. When receiving the request packet from the client, the NIC of the server forwards the request packet to the corresponding network card receiving queue according to the destination port number in the request packet, that is, the listening port number, that is, the first network card receiving queue. The host on the server side can obtain the to-be-received packet from the first NIC receiving queue.

Optionally, the server may further send a to-be-sent packet of the service according to the listening port number, that is, send a response packet of the service to the client. Specifically, the host on the server side can write the listening port number to the source port number field of the to-be-sent packet of the service; and send the to-be-sent packet to the network card sending queue. The network card sends the to-be-sent packet in the NIC sending queue.

It should be understood that, in various embodiments of the present invention, the size of the sequence numbers of the above processes does not mean the order of execution, and the order of execution of each process should be determined by its function and internal logic, and should not be taken to the embodiments of the present invention. The implementation process constitutes any limitation.

It should be understood that the specific examples of the embodiments of the present invention are only to be understood by those skilled in the art.

A method of processing a message according to an embodiment of the present invention is described in detail above, and a computer device according to an embodiment of the present invention will be described below.

FIG. 9 shows a schematic block diagram of a computer device 900 in accordance with an embodiment of the present invention.

As shown in FIG. 9, the computer device 900 can include a host 910 and a network card 920.

The host 910 is configured to obtain a first processor core identifier of the service binding, and the configured mapping relationship information, and determine, according to the first processor core identifier, a first local port number corresponding to the service, where the mapping relationship information is The mapping between the processor core identifier and the port number is performed, and the first local port number is written into the source port number field of the to-be-sent packet of the service, and the to-be-sent packet is sent to the network card sending queue.

The network card 920 is configured to send the to-be-sent packet in the network card sending queue.

The computer device of the embodiment of the present invention binds the service to the processor core identifier, and accordingly The port number corresponding to the service is determined, and the to-be-sent packet of the service is processed according to the port number, so that the network card can forward the to-be-received packet of the service to the corresponding network card queue according to the port number, thereby improving the forwarding efficiency of the packet. .

Optionally, in an embodiment of the present invention, the mapping relationship information includes a mapping relationship between a processor core identifier, a network card receiving queue, and a port number.

Optionally, in an embodiment of the invention, each processor core identifier corresponds to a plurality of port numbers.

Optionally, in an embodiment of the present invention, the host 910 is specifically configured to select the first local port number from the plurality of port numbers corresponding to the first processor core identifier.

Optionally, in an embodiment of the present invention, the host 910 is further configured to: configure the mapping relationship information.

Optionally, in an embodiment of the present invention, the network card 920 is further configured to receive a to-be-received packet of the service, where the destination port number in the to-be-received packet is the first local port number, according to the destination port. No. forwarding the to-be-received packet to the network card receiving queue corresponding to the first local port number;

The host 910 is further configured to obtain the to-be-received packet from the network card receiving queue corresponding to the first local port number.

Optionally, in an embodiment of the present invention, the computer device 900 is a client device, and the to-be-sent message includes a link request message;

The host 910 is further configured to bind the service to the first processor core identifier.

Optionally, in an embodiment of the present invention, the computer device 900 is a server, and the to-be-sent message includes a link accepting message;

The host 910 is further configured to bind the service to the first processor core identifier according to the listening port number of the service and the mapping relationship information;

The network card 920 is further configured to: receive a link request message of the service, where the destination port number in the link request message is the listening port number, and forward the to-be-received message to the listening port number according to the destination port number. Network card receiving queue;

The host 910 is further configured to obtain the link request message from the network card receiving queue corresponding to the listening port number.

In another embodiment of the present invention, the host 910 is configured to bind the service to the first processor core identifier according to the listening port number of the service and the configured mapping relationship information, where the mapping relationship information includes a processor. The mapping between the core identifier and the port number, the packet to be received of the service is obtained from the first network card receiving queue, where the first network card receiving queue is the first processor core identifier pair The appropriate network card receiving queue;

The network card 920 is configured to receive the to-be-received packet, and the destination port number in the to-be-received packet is the listening port number, and forward the to-be-received packet to the first network card receiving queue according to the destination port number.

Optionally, the host 910 is further configured to: write the listening port number to a source port number field of the to-be-sent packet of the service, and send the to-be-sent packet to the network card sending queue;

The network card 920 is further configured to send the to-be-sent packet in the network card sending queue.

It should be understood that the computer device 900, the host 910, and the network card 920 of the embodiments of the present invention may perform the corresponding processes in the foregoing method embodiments of the present invention. For brevity, no further details are provided herein.

It should be understood that host 910 can include a processor and a memory. The memory is for storing a program, and the processor is for executing a program for performing the method in the foregoing embodiments of the present invention.

It should be understood that in the embodiment of the present invention, the term "and/or" is merely an association relationship describing an associated object, indicating that there may be three relationships. For example, A and/or B may indicate that A exists separately, and A and B exist simultaneously, and B cases exist alone. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both, for clarity of hardware and software. Interchangeability, the composition and steps of the various examples have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

A person skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative For example, the division of the unit is only a logical function division, and the actual implementation may have another division manner, for example, multiple units or components may be combined or may be integrated into another system, or some features may be Ignore, or not execute. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, or an electrical, mechanical or other form of connection.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present invention.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention contributes in essence or to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

The above description is only a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto.

Claims

A method for processing a message, comprising:

Obtaining a first processor core identifier of the service binding;

Determining, according to the first processor core identifier, and the configured mapping relationship information, a first local port number corresponding to the service, where the mapping relationship information includes a mapping relationship between a processor core identifier and a port number;

Writing the first local port number into a source port number field of the to-be-sent packet of the service;

Sending the to-be-sent message to the network card sending queue.
The method according to claim 1, wherein the mapping relationship information comprises a mapping relationship between a processor core identifier, a network card receiving queue, and a port number.
The method of claim 1 or 2 wherein each processor core identifies a corresponding plurality of port numbers.
The method of claim 3, wherein the determining the first local port number comprises:

Selecting the first local port number from a plurality of port numbers corresponding to the first processor core identifier.
The method according to any one of claims 1 to 4, further comprising:

Obtaining a to-be-received packet of the service from the network card receiving queue corresponding to the first local port number, where the to-be-received packet is forwarded by the network card according to the destination port number in the to-be-received packet to the The NIC receiving queue corresponding to the first local port number.
The method according to any one of claims 1 to 5, wherein the to-be-sent message includes a link request message of the client;

Before the obtaining the first processor core identifier of the service binding, the method further includes:

Binding the service to the first processor core identity.
The method according to any one of claims 1 to 5, wherein the to-be-sent message includes a link accepting message on the server side;

Before the obtaining the first processor core identifier of the service binding, the method further includes:

And binding the service to the first processor core identifier according to the listening port number of the service and the mapping relationship information;

Obtaining a link request report of the service from a network card receiving queue corresponding to the listening port number Text.
A method for processing a message, comprising:

Binding the service to the first processor core identifier according to the listening port number of the service, and the configured mapping relationship information, where the mapping relationship information includes a mapping relationship between the processor core identifier and the port number;

Obtaining a to-be-received message of the service from the first network card receiving queue, where the first network card receiving queue is a network card receiving queue corresponding to the first processor core identifier.
The method of claim 8 further comprising:

Writing the listening port number to a source port number field of the to-be-sent packet of the service;

Sending the to-be-sent message to the network card sending queue.
A computer device, comprising:

a host, configured to obtain a first processor core identifier of the service binding, and determine, according to the first processor core identifier and the configured mapping relationship information, a first local port number corresponding to the service, where the mapping The relationship information includes a mapping relationship between the processor core identifier and the port number, and the first local port number is written in the source port number field of the to-be-sent packet of the service, and the to-be-sent packet is sent to the network card sending queue. ;as well as

And a network card, configured to send the to-be-sent packet in the network card sending queue.
The computer device according to claim 10, wherein the mapping relationship information comprises a mapping relationship between a processor core identifier, a network card receiving queue, and a port number.
A computer apparatus according to claim 10 or 11, wherein each processor core identifier corresponds to a plurality of port numbers.
The computer device according to claim 12, wherein the host is specifically configured to select the first local port number from among a plurality of port numbers corresponding to the first processor core identifier.
The computer device according to any one of claims 10 to 13, wherein the network card is further configured to receive a message to be received of the service, where a destination port number in the to-be-received message is Transmitting the to-be-received packet to the network card receiving queue corresponding to the first local port number according to the destination port number;

The host is further configured to obtain the to-be-received packet from a network card receiving queue corresponding to the first local port number.
A computer apparatus according to any one of claims 10 to 14, wherein The computer device is a client device, and the to-be-sent message includes a link request message;

The host is further configured to bind the service to the first processor core identifier.
The computer device according to any one of claims 10 to 14, wherein the computer device is a server, and the to-be-sent message includes a link acceptance message;

The host is further configured to bind the service to the first processor core identifier according to the listening port number of the service and the mapping relationship information;

The network card is further configured to: receive a link request message of the service, where the destination port number in the link request message is the listening port number, and forward the to-be-received message to the destination port number to The network card receiving queue corresponding to the listening port number;

The host is further configured to obtain the link request message from a network card receiving queue corresponding to the listening port number.
A computer device, comprising:

The host is configured to bind the service to the first processor core identifier according to the listening port number of the service and the configured mapping relationship information, where the mapping relationship information includes a mapping relationship between the processor core identifier and the port number. Obtaining a to-be-received message of the service from the first network card receiving queue, where the first network card receiving queue is a network card receiving queue corresponding to the first processor core identifier;

a network card, configured to receive the to-be-received packet, where the destination port number in the to-be-received packet is the listening port number, and forward the to-be-received packet to the first network card according to the destination port number. Receive queue.
The computer device according to claim 17, wherein the host is further configured to: write the listening port number into a source port number field of the to-be-sent packet of the service, and send the to-be-sent packet Send to the network card send queue;

The network card is further configured to send the to-be-sent packet in the network card sending queue.