{"id":104635,"date":"2022-07-12T09:36:46","date_gmt":"2022-07-12T07:36:46","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/dlya-yadra-linux-predlozhena-realizacziya-funkczii-memchr-rabotayushhaya-do-4-raz-bystree"},"modified":"2022-07-12T09:36:46","modified_gmt":"2022-07-12T07:36:46","slug":"dlya-yadra-linux-predlozhena-realizacziya-funkczii-memchr-rabotayushhaya-do-4-raz-bystree","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/dlya-yadra-linux-predlozhena-realizacziya-funkczii-memchr-rabotayushhaya-do-4-raz-bystree","title":{"rendered":"A memchr function implementation has been proposed for the Linux kernel that operates up to 4 times faster.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
A set of patches has been proposed for inclusion in the Linux kernel, featuring an optimized implementation of the memchr() function used for searching a character in an array. Unlike the previous version, which utilized byte-by-byte comparison, the proposed implementation is designed to fully utilize 64-bit and 32-bit CPU registers. Instead of bytes, comparison is performed using machine words, allowing for the comparison of at least 4 bytes at once. <\/p>\n
When searching through large strings, the new version has proven to be about 4 times faster than the old one (for example, with strings of 1000 characters). For smaller strings, the efficiency of the new implementation is not as significant, yet remains higher compared to the original version. In the Linux kernel, the size of strings processed by memchr() can reach up to 512 bytes. The performance increase for 512-byte strings, in cases where the searched character is located at the end of the string, is 20%. <\/p>\n
Testing the 5.18 kernel with the new version of «memchr()» for 32-bit and 64-bit architectures did not reveal any issues. The overall performance increase of the kernel subsystems using the optimized version of «memchr()» has not yet been assessed, nor has the feasibility of replacing the implementation been analyzed (the memchr() function call appears 129 times in the kernel code, including in driver and file system code). \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"