SSL communication processing device and SSL communication processing method

By distributing request queues across multiple child devices and using a round-robin selection method, the SSL communication processing device optimizes engine utilization, addressing underutilization issues and improving performance.

JP7577580B2Active Publication Date: 2024-11-05PFU LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2021045850
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-03-19
Publication Date
2024-11-05
Estimated Expiration
2041-03-19

AI Technical Summary

Technical Problem

Existing SSL communication processing devices fail to fully utilize the performance of encryption or decryption processing due to inefficient allocation of request queues and engines, leading to underutilization of resources and reduced performance.

Method used

The SSL communication processing device employs a request issuing core that issues requests to a plurality of grouped request queues, which are distributed across multiple child devices, allowing for parallel processing and round-robin selection of representative queues, ensuring balanced utilization of engines.

Benefits of technology

This approach maximizes the performance of SSL communication processing by effectively utilizing all engines and child devices, even in cases of load imbalance or device errors, thereby enhancing overall processing efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007577580000001
    Figure 0007577580000001
  • Figure 0007577580000002
    Figure 0007577580000002
  • Figure 0007577580000003
    Figure 0007577580000003
Patent Text Reader

Abstract

To provide an SSL communication processor that fully exhibits performance of a device that performs encryption processing or decryption processing of SSL communication.SOLUTION: An SSL communication processor includes: a request issuance core that issues a request for SSL communication encryption or decryption processing; a request queue aggregate that includes a plurality of request queues for queuing requests issued by the request issuing core; and a device that processes requests queued in the request queue. A plurality of grouped request queues are assigned to one of the request issuance cores.SELECTED DRAWING: Figure 2
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an SSL communication processing device and an SSL communication processing method. [Background technology]

[0002] For example, Patent Document 1 discloses an apparatus for ordering, synchronizing and scheduling work in a network services processor having multiple cores, in which each piece of work is identified by a tag indicating how the work should be synchronized and ordered, throughput is improved by processing work with different tags in parallel on different processor cores, packet processing can be divided into various stages, each stage has a different tag depending on ordering and synchronization constraints, tag switch operations initiated by the cores switch tags depending on the stage, and a dedicated tag switch bus minimizes the latency of the tag switch operations.

[0003] Patent document 2 also discloses a transmission control device in which a memory unit 1a stores information regarding the relationship between multiple requests and a priority for transmitting the request in association with the request, and when a processing unit 1b receives a first request for executing processing, it refers to the memory unit 1a to identify a second request related to the first request and a first priority corresponding to the second request, and the processing unit 1b transmits the second request at a second priority higher than the first priority to an information processing device 2 that executes processing according to the first request.

[0004] Patent document 3 also discloses a method of processing security operations, the method including a processor including a number of execution units that process a number of requests for security operations, the execution units outputting results of the number of requests to an output data structure associated with the requests in a remote memory based on pointers stored in the requests, the execution units being capable of outputting the results in an order different from the order of the requests in the request queue, the processor also including a request unit coupled to the execution units, the request unit fetching some of the requests from the request queue in the remote memory and fetching associated input data structures for some of the requests from the remote memory, and the request unit distributing the fetched requests to the number of execution units based on availability for processing by the execution units. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Special table 2008-512950 [Patent Document 2] Patent Publication No. 2019-040344 [Patent Document 3] Special table 2003-216591 Summary of the Invention [Problem to be solved by the invention]

[0006] The object of the present invention is to provide an SSL communication processing device that fully utilizes the performance of a device that performs encryption or decryption processing of SSL communication. [Means for solving the problem]

[0007] The SSL communication processing device of the present invention comprises a request issuing core that issues requests for encryption or decryption processing of SSL communication, a request queue collection including a plurality of request queues that queue the requests issued by the request issuing core, and a device that processes the requests queued in the request queues, and a plurality of grouped request queues are assigned to one of the request issuing cores.

[0008] Preferably, the request issuing core issues a request to a representative request queue among a plurality of grouped request queues, and a request queue selected in a round robin manner from among the grouped request queues queues the issued request to the representative request queue.

[0009] Preferably, the device includes a plurality of child devices capable of performing parallel processing independently of one another, and the grouped request queues are assigned to different child devices.

[0010] Preferably, the device includes more engines than the request queues.

[0011] In addition, the SSL communication processing method of the present invention includes a step of a request issuing core issuing a request for encryption or decryption processing of SSL communication to a group of request queues assigned to the request issuing core, a step of one of the request queues belonging to the group queuing the request issued by the request issuing core, and a step of a device performing encryption or decryption processing of SSL communication processing the request queued in the request queue. Effect of the Invention

[0012] This allows the performance of the device performing encryption or decryption processing of SSL communications to be fully utilized. [Brief description of the drawings]

[0013] [Figure 1] 1 is a diagram illustrating an example of a hardware configuration of a network device 1. [Diagram 2] 2 is a diagram illustrating an example of a functional configuration of a network device 1. [Diagram 3] 13 is a flowchart illustrating an SSL process (S10) in the network device 1. [Figure 4] 13 is a diagram illustrating an example of a functional configuration of a network device 1 in a modified example. [Diagram 5] FIG. 11 is a diagram illustrating a functional configuration of a network device in a first comparative example. [Figure 6] FIG. 11 is a diagram illustrating a functional configuration of a network device in a second comparative example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] An embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating an example of a hardware configuration of a network device 1. As shown in FIG. As illustrated in FIG. 1, the network device 1 includes a request issuing core 10, a request queue collection 12, and an SSL processing device 14. The request issuing core 10 issues requests for encryption or decryption processing of SSL (Secure Sockets Layer) communication. For example, the request issuing core 10 includes a plurality of request issuing cores, which issue requests in parallel. The request queue aggregate 12 includes a plurality of request queues 120, and queues requests issued from the request issuing core 10. Queuing refers to holding requests on a first-in, first-out basis. The SSL processing device 14 is an engine group including a plurality of engines that perform encryption or decryption processing of SSL communications, and processes the requests queued in the request queue group 12 in order. In the above configuration, a request for encryption processing, decryption processing, or the like is issued from the request issuing core 10 of the network device 1 to the request queue (request queue 120) of the SSL accelerator via the API. Requests queued in the request queue 120 are processed using the engine of the SSL accelerator (the engine of the SSL processing device 14) until the request is completed. The issuance and completion of a request are asynchronous, and the network device 1 issues a request every time it encrypts or decrypts received data.

[0015] (background) It is also possible to design the request issuing cores and the request queues in a one-to-one correspondence, as in Comparative Example 1 shown in Fig. 5. In this type of design, if the number of request queues is equal to or greater than the number of engines, there is no problem, but if the number of request queues is less than the number of engines, the engines will be left surplus and will not be used effectively. In addition, the request queue uses one free engine at a time to process one request. The free engine to be used is assigned automatically and cannot be controlled by software. That is, as shown in Fig. 5, the number of available request queues is less than the number of engines, resulting in free engines. Since the engines cannot be fully utilized, the SSL accelerator cannot demonstrate its original performance. In the example of Fig. 5, there are 6 request issuing cores and 30 request queues (of which 6 are available), and engines EN7 to EN30 cannot be used. There is no correlation between the request queue number and the engine number, and an available engine is automatically assigned.

[0016] Therefore, in the network device 1 of this embodiment, in the SSL accelerator, a plurality of request queues are grouped, and a request can be processed by issuing a request to a representative request queue of the group.

[0017] FIG. 2 is a diagram illustrating an example of the functional configuration of the network device 1. As shown in FIG. As illustrated in FIG. 2, the network device 1 has multiple request issuing cores 10, grouped request queues 120, and an SSL processing device 14 including multiple engines 140, with each request issuing core 10 assigned a grouped request queue 120. More specifically, a group of a plurality of request queues 120 is regarded as a node, and the same number of nodes are created as the number of request issuing cores 10. One representative request queue 122 is set for each node.

[0018] Fig. 3 is a flowchart explaining the SSL processing (S10) in the network device 1. Note that this flowchart will be explained focusing on one request issuing core 10 in Fig. 2. The other request issuing cores 10 also perform similar processing in parallel. As illustrated in FIG. 3, in step 100 (S100), the request issuing core 10 issues a request to the representative request queue 122 of the assigned request queue group (node). In step 110 (S110), the representative request queue 122 selects a request queue 120 assigned to the group (node) to which it belongs, and issues a request to the request queue 120. The selection method is round robin.

[0019] In step 120 (S120), the selected request queue 120 queues the issued request. In step 130 (S130), the engine 140 of the SSL processing device 14 processes the requests queued in the request queue 120.

[0020] As described above, according to the network device 1 of this embodiment, by increasing the number of request queues 140 used in the SSL accelerator and increasing the number of requests issued, the engines 140 can be effectively utilized and the performance of the SSL accelerator can be demonstrated. In other words, it is possible to create a state in which the number of request queues 120 is equal to or greater than the number of engines 140, and the relationship between the request issuing cores and the request queues becomes 1:many. 2, the request issuing core 10 can issue requests from a number of request queues 120, the number of which is at least the number of request queues 120 or engines 140. For example, when a request is queued in the representative request queue 122, one of the five request queues 120, including the representative request queue, namely, the 1st, 7th, 13th, 19th, and 25th request queues is selected and the request is issued. In FIG. 2, an arrow is drawn from the request queue 120 to the engine for the request issued from the request issuing core 10, but an arrow can be drawn from the request queue 120 to the engine 140 for the requests issued from the other request issuing cores 10. This allows the engines to be used effectively without waste. Note that there is no correlation between the numbers of the request queues 120 and the numbers of the engines 140, and an available engine 140 is automatically assigned.

[0021] (Modification) Next, as a modification of the above embodiment, a case will be described in which the SSL accelerator is physically one device but has an internal structure having three child devices. In this case, if there is a bias in the request issuing cores used during communication, there will be a bias in the child devices used, as shown in Fig. 6. More specifically, a case in which two request issuing cores are evenly assigned to each of three child devices A, B, and C in Fig. 6 will be described as Comparative Example 2. The engines of each child device are denoted as A1 to A10, B11 to B20, and C21 to C30. Considering a case where the request issuing cores 1 to 4 are biased, the request issuing cores 1 and 2 are assigned only to child device A. In this case, among the engines A1 to A10, an available engine is automatically assigned and used. Furthermore, the request issuing cores 3 and 4 are assigned only to child device B. In this case, among the engines B11 to B20, an available engine is used. As a result, the engines are biased toward child devices A and B, and child device C is hardly used at all, and only about two-thirds of its original performance as an SSL accelerator is achieved.

[0022] There are two aspects to this lack of performance: -Lack of performance when engine is under heavy load For example, if there is a concentration of requests with a large volume and heavy calculations that require processing by all 30 engines, and the requests are concentrated on child devices A and B, the number of engines that can be used will be limited to 20: A1 to A10 and B11 to B20. Since all 30 engines cannot be used, the inherent performance of the SSL accelerator cannot be achieved. -Cannot fully utilize the unique features of each child device Each child device has its own unique functions in addition to the engine. For example, when processing a specific encryption type, calculations may be performed using a unique circuit that each child device has, separate from the engine. As a result, while three circuits are available for all devices, only two circuits are used for two devices, and performance cannot be achieved. This problem does not only occur during high loads such as those described above.

[0023] Therefore, in the network device 1 of this modification, a plurality of grouped request queues 120 are assigned to different child devices. In other words, a plurality of request queues 120 in a group are assigned across a plurality of child devices. More specifically, as shown in Fig. 4, the request queues 120 and engines 140 of each child device are used as evenly as possible to maximize performance.

[0024] Specifically, an example of an SSL accelerator having multiple child devices is the PE3ISLBTL (PCIe 3.0, x8 Crypto / Compression LBG Server Adapter) made by Silicon Corporation. In such an SSL accelerator, the request queues 120 of the child devices are assigned to the request issuing core 10 so as to be used as evenly as possible. In this modified example, the number of request issuing cores 10 is six, the number of child devices is three, the request queues 120 of child device A are 1 to 10, the engine group 15A of child device A are A1 to A10, the request queues 120 of child device B are 11 to 20, the engine group 15B of child device B are B11 to B20, the request queues of child device C are 21 to 30, and the engine group 15C of child device C are C21 to C30. Note that the queue numbers of the representative request queue 122 are indicated by circles. There is no relationship between the numbers of the request queues 120 and the numbers of the engines 140, and a request queued in the request queue 120 is automatically assigned an available engine 140 from among the engines 140 indicated by the same hatching pattern as the request queue 120.

[0025] The above settings have the following effects: Even if the request issuing cores 10 used are biased, processing can be distributed among child devices, so processing can be performed without degrading the performance of the SSL processing device 14. For example, even if the request issuing cores used are biased toward numbers 1 to 4, in this modification, all three child devices A to C can be used from the request queues 120 corresponding to each request issuing core 10, so that the unique functions of all child devices can be used. Also, all engines 140 of all child devices can be used. Therefore, performance degradation can be reduced compared to when not using all child devices. Even if an error occurs in one child device and it becomes temporarily unable to process, other child devices can process requests, so processing can continue. For example, if child device A becomes unable to process, request queues 120 Nos. 1 to 10 become unusable, but request queues 120 Nos. 11 to 30 can be used, so all request issuing cores 10 can continue to issue and process requests.

[0026] In this manner, according to the network device 1 of this modification, even if the request issuing cores 10 used are unevenly distributed, processing can be distributed among child devices, so that processing can be performed without degrading the performance of the SSL accelerator as a whole. Furthermore, even if an error occurs in one child device and it becomes temporarily unable to process, other child devices can still process the request, allowing processing to continue. [Explanation of symbols]

[0027] 1...Network equipment 10…Request issuing core 12...Request queue cluster 120...Request queue 122…Representative request queue 14. SSL processing device 140…Engine 15…Engines

Claims

1. a request issuing core that issues a request for encryption or decryption of SSL communication; a request queue assembly including a plurality of request queues for queuing requests issued by the request issuing core; a device for processing requests queued in the request queue; having A plurality of grouped request queues are assigned to one of the request issuing cores. SSL communications processing device.

2. the request issuing core issues a request to a representative request queue among the grouped request queues; Among the grouped request queues, a request queue selected in a round robin manner queues the request issued to the representative request queue. The SSL communications processing device according to claim 1 .

3. The device includes a plurality of child devices that can operate in parallel independently of each other; The grouped request queues are assigned to different child devices. The SSL communications processing device according to claim 1 .

4. The device includes more engines than the request queue. The SSL communications processing device according to claim 2 .

5. A request issuing core issues a request for encryption or decryption of SSL communication to a group of request queues assigned to the request issuing core; queuing a request issued by the request issuing core in one of the request queues belonging to the group; A device that performs encryption or decryption processing of SSL communication processes requests queued in the request queue. The SSL communication processing method includes the steps of:

Citation Information

Patent Citations

  • Limited priority queue scheduler

    JP2001292172A

  • Interface for security coprocessor

    JP2003216591A

  • Packet queuing, scheduling and ordering

    JP2008512950A

  • Method and apparatus for scheduling in multiprocessing environment

    JP2017521806A

  • Transmission control program, transmission control apparatus and transmission control method

    JP2019040344A