An efficiency optimization method based on glamor acceleration

Abstract

The application discloses an efficiency optimization method based on Glamor acceleration, relates to the technical field of computer graphics, and determines the drawing mode of an application by constructing an application name whitelist, adopts Glamor drawing for the application which does not conform to the application name whitelist to fully utilize the acceleration capacity of a GPU, determines the drawing mode of the application which conforms to the application name whitelist through application resources, comprehensively evaluates whether software drawing is adopted through a preset threshold, simultaneously, the system constructs a Glamor data storage area, realizes dynamic management of drawing data, the storage area is used for storing historical drawing data and is used for searching and comparing in subsequent drawing requests, and through the drawing mode selection mechanism of the application name whitelist, the application resource determination mechanism and the drawing data dynamic management mechanism, efficient drawing processing is realized in complex drawing requests, the overall graphic rendering performance is improved, and meanwhile, the effective utilization of system resources is ensured.

Description

TECHNICAL FIELD

[0001] The application relates to the technical field of computer graphics, in particular to an efficiency optimization method based on Glamor acceleration. BACKGROUND

[0002] Two-dimensional graphics acceleration is an important field in computer graphics processing, mainly to improve the efficiency and performance of two-dimensional graphics rendering, with the wide application of graphical user interface and the popularity of multimedia content, the demand for graphics processing speed and quality is increasing, two-dimensional graphics acceleration technology arises at the historic moment;

[0003] In the Linux system, EXA and Glamor are two common two-dimensional graphics acceleration frameworks, EXA optimizes graphics operations by providing acceleration primitives, while Glamor uses OpenGL to accelerate 2D graphics operations, and realizes hardware acceleration through a unified OpenGL interface, the application of these technologies has significantly improved the performance and user experience of modern graphical interface;

[0004] EXA and Glamor are two 2D graphics acceleration architectures, each has its own advantages and disadvantages, EXA is more traditional and focuses on specific 2D operation optimization, while Glamor uses OpenGL to provide more general and powerful acceleration capabilities, however, for simple 2D operations such as text drawing and small graphics filling, Glamor needs to allocate additional video memory and memory to store buffers, textures and perform OpenGL operations, which consumes more resources, therefore, it has important practical significance to develop an efficiency optimization method based on Glamor acceleration. SUMMARY

[0005] The application aims to provide an efficiency optimization method based on Glamor acceleration to solve the problems in the background art.

[0006] In order to achieve the above-mentioned purpose, the application provides the following technical scheme: an efficiency optimization method based on Glamor acceleration, comprising:

[0007] Establishing an application name whitelist, when the system receives a drawing request, obtaining the application name of the drawing request and selecting a drawing method by comparing the application name with the application name whitelist;

[0008] When the application name meets the application name whitelist, judging the application resources to obtain the drawing method;

[0009] Performing Glamor drawing operation on the application that meets the Glamor drawing, and dynamically managing the drawing data;

[0010] Performing software drawing operation on the application that meets the software drawing.

[0011] In a preferred embodiment, the step of establishing an application name whitelist, and when the system receives a drawing request, obtaining the name of the application that issued the drawing request and selecting the drawing method by referring to the application name whitelist, is as follows:

[0012] Create an application name whitelist;

[0013] When the system receives a drawing request, it obtains the drawing request information and then retrieves the name of the application that issued the request based on the drawing request information.

[0014] The application name is compared with the application name whitelist. If the application name is in the whitelist, the rendering method is determined by the application resources.

[0015] If the application name is not in the whitelist, Glamor drawing will proceed directly.

[0016] In a preferred embodiment, the step of determining the rendering method for application resources when the application name matches the application name whitelist is as follows:

[0017] First, define the preset thresholds, including preset width and height thresholds, preset fill type, preset usage type, and preset color depth thresholds;

[0018] The application resources are judged based on preset thresholds, and the drawing method is selected accordingly.

[0019] In a preferred embodiment, the step of determining the application resources based on a preset threshold and selecting the rendering method is as follows:

[0020] The application resources, including the width and height of the drawn image, fill type, usage type, and color depth, are obtained through the drawing request information.

[0021] If the width and height of the drawn image are lower than the preset width and height thresholds, the image will be drawn by software; otherwise, the fill type will be determined.

[0022] If the fill type meets the preset fill type threshold, software drawing is performed; otherwise, usage type is determined.

[0023] If the usage type matches the preset usage type, software drawing is performed; otherwise, color depth is judged.

[0024] If the color depth is lower than the preset color depth threshold, software drawing is performed; if it is higher, Glamor drawing is performed.

[0025] In a preferred embodiment, the steps of performing Glamor rendering operations on applications that satisfy Glamor rendering and dynamically managing the rendering data are as follows:

[0026] Construct a Glamor data storage area to store historical Glamor drawing data;

[0027] Select the Glamor drawing process by retrieving the Glamor data storage area.

[0028] In a preferred embodiment, the step of selecting the Glamor drawing process by retrieving the Glamor data storage area is as follows:

[0029] Upon receiving a Glamor drawing request, retrieve the Glamor data storage area;

[0030] If the Glamor data storage area contains historical Glamor drawing data, then a data comparison is performed;

[0031] If the Glamor drawing request information is the same as the historical Glamor drawing data, then the historical Glamor drawing data will be used directly for the Glamor drawing operation.

[0032] If they are different, create a Pixmap and allocate memory;

[0033] Receive Glamor drawing requests and convert them into OpenGL commands;

[0034] Based on the Glamor drawing request information, the Pixmap texture is bound, drawing operations are performed through OpenGL instructions, and the drawing data is stored in the Glamor data storage area;

[0035] Image processing and compositing are performed using OpenGL shaders.

[0036] In a preferred embodiment, the step of performing software drawing operations on the application that meets the software drawing requirements is as follows:

[0037] Receive software drawing requests and obtain software drawing request information;

[0038] Encapsulate software drawing request information into an image object that can be manipulated by Pixman;

[0039] Use pixman to perform 2D drawing operations on the image object;

[0040] After completing the 2D drawing operations, release the pixman image and system-allocated resources.

[0041] The technical effects and advantages provided by the present invention in the above technical solution are as follows:

[0042] 1. This invention effectively improves rendering efficiency by constructing an application name whitelist and using a rendering method selection mechanism based on this whitelist. By determining whether the requesting application is on the whitelist and combining this with preset thresholds, fill types, and other resource characteristics, the rendering method is selected, making the system more accurate in handling rendering requests within a certain range. For applications that meet the conditions, Glamor rendering is performed, leveraging the parallel processing capabilities of the GPU to significantly shorten the rendering response time. For requests that do not meet the Glamor rendering conditions, software rendering is used directly, avoiding the overhead of Glamor rendering. Therefore, whether through dynamic management and real-time judgment or by optimizing the judgment mechanism, this technical solution effectively improves rendering speed and efficiency, meeting the demands of modern applications for high-performance graphics processing and improving the user experience.

[0043] 2. This invention demonstrates flexible resource management capabilities by defining a dynamic management mechanism for Glamor rendering data and real-time assessment of current resource status. A Glamor data storage area is constructed to store historical rendering data, which is then compared in subsequent rendering requests. This effectively reduces repetitive rendering operations. When a received rendering request matches historical data, the system can directly call the existing data for rendering, which not only improves performance but also saves memory and computing resources. If the data differs, the system allocates the corresponding memory based on the latest request and performs rendering. This flexible resource management ensures that the system maintains high responsiveness under high load, contributing to improved system stability and durability, and meeting the high-efficiency, low-latency rendering needs of various applications. Attached Figure Description

[0044] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this invention. For those skilled in the art, other drawings can be obtained based on these drawings.

[0045] Figure 1 This is a flowchart of the method of the present invention. Detailed Implementation

[0046] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0047] Example 1, please refer to Figure 1 As shown in this embodiment, an efficiency optimization method based on Glamor acceleration includes:

[0048] S1. Establish an application name whitelist. When the system receives a drawing request, it obtains the application name that issued the drawing request and selects the drawing method according to the application name whitelist.

[0049] S2. When the application name matches the application name whitelist, the application resources are judged to obtain the drawing method.

[0050] S3. Perform Glamor drawing operations on applications that meet the requirements for Glamor drawing and dynamically manage the drawing data;

[0051] S4. Perform software drawing operations on applications that meet the software drawing requirements;

[0052] As described in steps S1-S4 above, 2D graphics acceleration is an important area in computer graphics processing, primarily aimed at improving the efficiency and performance of 2D graphics rendering. With the widespread application of graphical user interfaces and the proliferation of multimedia content, the demand for graphics processing speed and quality is constantly increasing, leading to the emergence of 2D graphics acceleration technologies. In Linux systems, EXA and Glamor are two common 2D graphics acceleration frameworks. EXA optimizes graphics operations by providing acceleration primitives, while Glamor utilizes OpenGL to accelerate 2D graphics operations, implementing hardware acceleration through a unified OpenGL interface. The application of these technologies has significantly improved the performance and user experience of modern graphical interfaces. EXA and Glamor... As two 2D graphics acceleration architectures, EXA and Glamor each have their advantages and disadvantages. EXA is more traditional, focusing on specific 2D operation optimizations, while Glamor utilizes OpenGL to provide more general and powerful acceleration capabilities. However, for simple 2D operations such as text drawing and small graphic filling, Glamor requires additional allocation of video memory and system memory to store buffers, textures, and perform OpenGL operations, resulting in greater resource consumption. This invention effectively improves drawing efficiency by constructing an application name whitelist and a drawing mode selection mechanism based on the application name whitelist. By determining whether the requesting application is in the whitelist, and combining it with preset thresholds, fill types, and other resource characteristics, the drawing mode is selected, making the system more accurate in handling drawing requests within a certain range. For applications that meet the requirements, Glamor rendering is performed, leveraging the parallel processing capabilities of the GPU to significantly shorten rendering response time. For requests that do not meet the Glamor rendering requirements, software rendering is used directly, avoiding the overhead of Glamor rendering. Based on this, whether through dynamic management and real-time judgment or through optimized judgment mechanisms, the rendering speed and efficiency of this technical solution are effectively improved, adapting to the high-performance graphics processing needs of modern applications and improving user experience. Simultaneously, defining a dynamic management mechanism for Glamor rendering data and real-time judgment of current resource status demonstrates flexible resource management capabilities. A Glamor data storage area is constructed to store historical rendering data, and data comparison is performed in subsequent rendering requests, effectively reducing redundant rendering operations. When a received rendering request matches historical data, the system can directly call the existing data for rendering, which not only improves performance but also saves memory and computing resources. If the data differs, the system allocates the corresponding memory according to the latest request and performs rendering. This flexible resource management ensures that the system maintains high response efficiency under high load, contributing to improved system stability and durability, and meeting the high-efficiency, low-latency rendering needs of different applications.

[0053] In one embodiment, step S1, which involves establishing an application name whitelist and, when the system receives a drawing request, obtaining the name of the application that issued the drawing request and selecting the drawing method by referring to the application name whitelist, includes:

[0054] S11. Create an application name whitelist;

[0055] S12. When the system receives a drawing request, it obtains the drawing request information and obtains the application name that issued the request based on the drawing request information;

[0056] S13. Compare the application name with the application name whitelist. If the application name is in the whitelist, determine the drawing method through the application resources.

[0057] S14. If the application name is not in the whitelist, Glamor drawing will be performed directly.

[0058] As described in steps S11-S14 above, a simple text file format or database structure is used to store application names, such as a CSV file or JSON format, where each row or entry represents a allowed application name. Commonly used graphical applications are collected, including but not limited to the following: xrandr, xsetroot, GIMP, Inkscape, LibreOfficeDraw, Firefox, Chromium, Evince, Okular, xterm, gnome-terminal, etc. At system startup, the whitelist file is read and loaded into memory for fast lookup. The system receives drawing requests from various applications via IPC, socket, or other communication protocols. It extracts key information from the drawing requests, including the application name and detailed information about the drawing content, such as image size and fill type. The system compares the obtained application name with a whitelist of application names previously loaded into memory. Hash tables or other efficient data structures can be used to speed up the lookup process. If the application name is not in the whitelist, Glamor drawing is performed directly. If the application name is in the whitelist, other resource information, such as the requested image width, height, fill type, usage type, etc., is further extracted from the request to prepare for the next step of resource determination.

[0059] In one embodiment, step S2, which involves determining the application resource and obtaining the rendering method when the application name matches the application name whitelist, includes:

[0060] S21. First, define the preset thresholds, including preset width and height thresholds, preset fill type, preset usage type, and preset color depth thresholds;

[0061] S22. Determine the application resources based on the preset threshold and select the drawing method;

[0062] As described in steps S21-S22 above, a standard width and height threshold is determined to determine whether the image requested for drawing is suitable for software drawing. For example, the width and height thresholds can be set to 32 pixels. This threshold should be adjusted according to the actual application scenario and testing to ensure optimal performance under different device configurations. A list of fill types that support software drawing is defined, such as FillTiled, FillStippled, or FillOpaqueStippled, and these three types are more efficient when using software drawing. Request types suitable for software drawing are listed, such as GLAMOR_CREATE_PIXMAP_CPU, CREATE_PIXMAP_USAGE_GLYPH_PICTURE, and CREATE_PIXMAP_USAGE_SHARED, and these three types are also more efficient when using software drawing. An acceptable color depth threshold is specified. If the color depth is less than or equal to this threshold, software drawing is selected. This threshold should be adjusted according to the actual application scenario and testing.

[0063] In one embodiment, step S22, which determines the application resources based on a preset threshold and selects the rendering method, includes:

[0064] S221. Obtain application resources, including the width and height of the drawn image, fill type, usage type, and color depth, through the drawing request information;

[0065] S222. When the width and height of the drawn image are lower than the preset width and height thresholds, software drawing is performed; if they are higher, the fill type is determined.

[0066] S223. If the fill type meets the preset fill type threshold, then the software will draw; otherwise, the usage type will be judged.

[0067] S224. If the usage type matches the preset usage type, then software drawing is performed; otherwise, color depth is judged.

[0068] S225. When the color depth is lower than the preset color depth threshold, software drawing is performed; if it is higher, Glamor drawing is performed.

[0069] As described in steps S221-S225 above, the system extracts drawing request information from the received drawing request. This typically includes, but is not limited to, the width of the image to be drawn (in pixels), the height of the image to be drawn (in pixels), the current fill type (e.g., fill color, pattern), the current usage type of the request (e.g., Glamor-related creation, sharing), and the color depth of the image to be drawn (typically in bits, representing the number of bits per pixel). Then, the system uses conditional judgment to test the image width and height. If both the image width and height are less than or equal to a preset threshold, software drawing is selected. If either dimension exceeds the preset value, the system proceeds to the next judgment step, checking the fill type to see if it meets the preset conditions. If the fill type meets the conditions for software drawing, the system uses the CPU for drawing to avoid the additional overhead of using Glamor. If the conditions are not met, the system proceeds to the next step. The system determines the usage type in the request and checks if it meets preset conditions. If the usage type meets the conditions, software rendering is selected; otherwise, the color depth is checked to ensure rendering quality and performance. The system also checks if the color depth in the request is below a preset depth threshold. If the color depth is less than or equal to the preset threshold, software rendering is selected to improve performance and reduce resource consumption. If the color depth is high, Glamor rendering is used, and the drawing task is handled by the GPU to achieve higher rendering quality. Based on this meticulous design, the system can flexibly determine which rendering method to use according to the characteristics of different application resources and preset thresholds. This condition-based selection mechanism ensures efficient decision-making in various rendering requests, enabling the system to flexibly adapt to different application needs while ensuring performance, thereby achieving the best user experience.

[0070] In one embodiment, step S3, which involves performing Glamor drawing operations on applications that satisfy Glamor drawing requirements and dynamically managing the drawing data, includes:

[0071] S31. Construct a Glamor data storage area to store historical Glamor drawing data;

[0072] S32. Select the Glamor drawing process by retrieving the Glamor data storage area;

[0073] As described in steps S31-S32 above, define the structure and type of the data storage area, and select an appropriate data structure such as a hash table, mapping, or database system to store historical Glamor drawing data. The data structure should be selected based on the application's access frequency and data volume to optimize lookup and storage performance. Each piece of historical Glamor drawing data should contain key drawing information, including: application name (indicating which application the drawing request came from), drawing request parameters (such as image width and height, fill type, and usage type), drawing data (saving texture or buffer data generated by the drawing operation), and timestamp (recording the time of the drawing request for subsequent management and cleanup). At system startup, instantiate the Glamor data storage area and read any possible previous drawing data for initialization. Implement a periodic saving mechanism to persist the drawing data to disk or database to prevent data loss in case of system crashes or restarts. Simultaneously, design a dynamic management strategy to periodically clean up expired or unused drawing data, such as using an LRU algorithm to determine which objects to delete, to maintain the efficiency of the storage area. Select the Glamor drawing process based on the data in the Glamor data storage area.

[0074] In one embodiment, step S32, which involves selecting a Glamor drawing process by retrieving a Glamor data storage area, includes:

[0075] S321. Upon receiving a Glamor drawing request, retrieve the Glamor data storage area;

[0076] S322. If the Glamor data storage area contains historical Glamor drawing data, then perform a data comparison.

[0077] S323. If the Glamor drawing request information is the same as the historical Glamor drawing data, then the historical Glamor drawing data is used directly to perform the Glamor drawing operation.

[0078] S324. If they are not the same, create a Pixmap and allocate memory.

[0079] S325: Receive Glamor drawing requests and convert them into OpenGL commands;

[0080] S326. Bind the Pixmap texture based on the Glamor drawing request information, perform drawing operations through OpenGL instructions, and save the drawing data in the Glamor data storage area;

[0081] S327. Image processing and compositing using OpenGL shaders;

[0082] As described in steps S321-S327 above, the system receives Glamor drawing requests from applications in real time via an internal message queue or IPC mechanism. The request should contain all parameters required for drawing, such as application name, image specifications, fill type, and color depth. Upon receiving the request, the system quickly accesses the Glamor data storage area and searches for corresponding historical drawing data using the application name and drawing parameters in the request. The system checks whether the Glamor data storage area contains historical drawing data. If no historical data exists, there is no need for comparison, and the system proceeds directly to the step of creating new data. If historical data exists, the system extracts the relevant parameters, such as image size, fill type, usage type, and color depth, and compares them with the relevant parameters in the drawing request. If the data in the drawing request is exactly the same as the historical Glamor data in the storage area, the historical drawing data is used directly for Glamor drawing operations, avoiding redundant processing. Simultaneously, the displayed content is updated to ensure users see immediate rendering results. If historical data differs from the current drawing request, the system creates a new Pixmap object, allocates appropriate memory via system calls to meet the image specifications defined in the drawing request, converts the received Glamor drawing request into commands understandable by OpenGL (e.g., setting canvas, primitive type, fill state, etc.), binds the newly created Pixmap to a texture in the current OpenGL context, draws the image using the passed drawing request information, executes OpenGL drawing commands, performs specific drawing operations using OpenGL commands, and displays the results on the screen. After drawing is complete, the data of this execution result is saved to the Glamor data storage area for use in the next identical request. Then, additional image processing and compositing operations are performed using OpenGL shaders, such as color conversion, texture mapping, and post-processing effects, which can flexibly handle different special effects requirements. Complex effects can be achieved by setting appropriate shader programs and executing steps such as set uniforms. Finally, the processed image is correctly rendered in the user interface, and the final result is output to improve the user experience.

[0083] In one embodiment, step S4, which involves performing software drawing operations on an application that satisfies software drawing requirements, includes:

[0084] S41. Receive software drawing request and obtain software drawing request information;

[0085] S42. Encapsulate the software drawing request information into a Pixman-operable image object;

[0086] S43. Call pixman to perform 2D drawing operations on the image object;

[0087] S44. After completing the 2D drawing operation, release the pixman image and system-allocated resources;

[0088] As described in steps S41-S44 above, the software drawing request information is obtained, including the image's width, height, fill color, image format, and drawing type. Then, a new Pixman image object is created using the Pixman library's API, providing the basic structure for subsequent drawing operations. Simultaneously, based on the fill color and type in the request, the relevant attributes of the Pixman image object are set. After setting, the Pixman API is called to perform 2D drawing operations on the created image object. Depending on the drawing type used, such as Solid or Tiled, the corresponding Pixman drawing operation method is called. Based on the drawing result, the image data in the Pixman image object is updated to achieve the desired visual effect. After the 2D drawing operation is completed, necessary cleanup work is performed. The Pixman image object and related allocated resources are released to prevent memory leaks. If memory was allocated for other operations during the drawing process, it is ensured to be released accordingly. Finally, the drawing completion information is returned to the original requesting application, informing it that the drawing operation has been successfully completed. Image data can also be sent back to the application or the application's display content can be updated to ensure the user can see the final effect.

[0089] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An efficiency optimization method based on Glamor acceleration, characterized in that: Establish an application name whitelist. When the system receives a drawing request, it obtains the name of the application that issued the drawing request and selects the drawing method by referring to the application name whitelist. When the application name matches the application name whitelist, the application resources are judged to obtain the rendering method; Perform Glamor drawing operations on applications that meet the requirements for Glamor drawing and dynamically manage the drawing data; Perform software drawing operations on applications that meet the requirements of software drawing; The steps for performing Glamor rendering operations on applications that meet the Glamor rendering requirements and dynamically managing the rendering data are as follows: Construct a Glamor data storage area to store historical Glamor drawing data; Select the Glamor drawing process by retrieving the Glamor data storage area; Upon receiving a Glamor drawing request, retrieve the Glamor data storage area; If the Glamor data storage area contains historical Glamor drawing data, then a data comparison is performed; If the Glamor drawing request information is the same as the historical Glamor drawing data, then the historical Glamor drawing data will be used directly for the Glamor drawing operation. If they are different, create a Pixmap and allocate memory; Receive Glamor drawing requests and convert them into OpenGL commands; Based on the Glamor drawing request information, the Pixmap texture is bound, drawing operations are performed through OpenGL instructions, and the drawing data is stored in the Glamor data storage area; Image processing and compositing are performed using OpenGL shaders.

2. The efficiency optimization method based on Glamor acceleration according to claim 1, characterized in that: The steps for establishing an application name whitelist, where the system obtains the name of the application that issued the drawing request and selects the drawing method by referring to the application name whitelist when it receives a drawing request, are as follows: Create an application name whitelist; When the system receives a drawing request, it obtains the drawing request information and then retrieves the name of the application that issued the request based on the drawing request information. The application name is compared with the application name whitelist. If the application name is in the whitelist, the rendering method is determined by the application resources. If the application name is not in the whitelist, Glamor drawing will proceed directly.

3. The efficiency optimization method based on Glamor acceleration according to claim 1, characterized in that: The steps for determining the rendering method of application resources when the application name matches the application name whitelist are as follows: First, define the preset thresholds, including preset width and height thresholds, preset fill type, preset usage type, and preset color depth thresholds; The application resources are judged based on preset thresholds, and the drawing method is selected accordingly.

4. The efficiency optimization method based on Glamor acceleration according to claim 3, characterized in that: The steps for determining application resources and selecting the rendering method based on a preset threshold are as follows: The application resources, including the width and height of the drawn image, fill type, usage type, and color depth, are obtained through the drawing request information. If the width and height of the drawn image are lower than the preset width and height thresholds, the image will be drawn by software; otherwise, the fill type will be determined. If the fill type meets the preset fill type threshold, software drawing is performed; otherwise, usage type is determined. If the usage type matches the preset usage type, software drawing is performed; otherwise, color depth is judged. If the color depth is lower than the preset color depth threshold, software drawing is performed; if it is higher, Glamor drawing is performed.

5. The efficiency optimization method based on Glamor acceleration according to claim 1, characterized in that: The steps for performing software drawing operations on applications that meet the software drawing requirements are as follows: Receive software drawing requests and obtain software drawing request information; Encapsulate software drawing request information into an image object that can be manipulated by Pixman; Use pixman to perform 2D drawing operations on the image object; After completing the 2D drawing operations, release the pixman image and system-allocated resources.

Images