GitMensch commented on issue #30368: URL: https://github.com/apache/arrow/issues/30368#issuecomment-3322491072
Just rechecked... the code is still identical: https://github.com/apache/arrow/blob/37c87db36b5d076deba4ade73822270ccd0640ea/cpp/src/arrow/util/cpu_info.cc#L394-L419 reads /proc/cpuinfo, which gets the general information about what the processor is capable of which is then parsed at https://github.com/apache/arrow/blob/37c87db36b5d076deba4ade73822270ccd0640ea/cpp/src/arrow/util/cpu_info.cc#L343-L383 A program can use cpuid faulting to mask features for the current run (valgrind and RR both do this) _and_ checking via `cpuid` should be faster than reading and parsing the "file" in the first place. .... not sure if @pitrou may work on a PR, but that still seems a reasonable thing to do (I'm not even an arrow-user, but still interested in the patch to learn more about how that would be coded :-) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
