gsoc:2024-gsoc-perf

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
gsoc:2024-gsoc-perf [2024/02/08 04:58]
namhyung
gsoc:2024-gsoc-perf [2024/02/08 05:08] (current)
namhyung [Data type profiling]
Line 87: Line 87:
  
 Data type profiling is a new technique to show memory access profiles with type information. ​ See [[https://​lwn.net/​Articles/​955709/​ | LWN article]] for more detail. ​ It's still in the early stage and has a lot of room for improvement. ​ For example, it needs to support C++ and other languages, better integration to other perf commands like ''​annotate''​ and ''​c2c'',​ performance optimization,​ other architecture support and so on.  It'd be ok if you're not familiar with ELF or DWARF format. Data type profiling is a new technique to show memory access profiles with type information. ​ See [[https://​lwn.net/​Articles/​955709/​ | LWN article]] for more detail. ​ It's still in the early stage and has a lot of room for improvement. ​ For example, it needs to support C++ and other languages, better integration to other perf commands like ''​annotate''​ and ''​c2c'',​ performance optimization,​ other architecture support and so on.  It'd be ok if you're not familiar with ELF or DWARF format.
 +
 +==== perf trace and BTF ====
 +
 +  * complexity: intermediate or hard
 +  * duration: medium or large
 +  * requirements:​ machine to work and test on. C programming,​ BPF
 +
 +''​perf trace''​ is similar to ''​strace''​ but much performant since it doesn'​t use ptrace. ​ So it needs to capture and understand the format of syscall arguments as ''​strace''​ does.  Right now, it has to build a list of format to pretty-print the syscall args.  But we find it limited and manual work.  Instead, it could use BTF (BPF type format) which has all the type information and is available in the (most) kernel.
  
gsoc/2024-gsoc-perf.1707368301.txt.gz · Last modified: 2024/02/08 04:58 by namhyung