netbird/gvisor
0
0
Fork 0
mirror of https://github.com/netbirdio/gvisor.git synced 2026-05-22 17:12:49 -07:00
Code Issues Packages Projects Releases Wiki Activity

Fix second systrap blogpost image.

Browse Source 
getpid-ptrace-vs-systrap-unopt.svg was a copy of getpid-ptrace-vs-native.svg.
Rename image so previously cached image isn't reused.

PiperOrigin-RevId: 528499423
This commit is contained in:
Konstantin Bogomolov
2023-05-01 10:04:04 -07:00
committed by gVisor bot
parent 1aa75b6714
commit 8218095436
3 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
website/assets/images/2023-04-28-getpid-ptrace-vs-systrap-unopt.svg
-1
View File
File diff suppressed because one or more lines are too long
Side by Side

Before

Width:  |  Height:  |  Size: 89 KiB

website/assets/images/2023-04-28-getpid-ptrace-vs-systrap-unoptimized.svg
+1
View File
File diff suppressed because one or more lines are too long
Side by Side

After

Width:  |  Height:  |  Size: 92 KiB

website/blog/2023-04-28-systrap-release.md
+1 -1
View File
@@ -77,7 +77,7 @@ populates shared memory regions, and requests the sentry to handle the requested
system call. This alone proved to be faster than using `PTRACE_SYSEMU`, as
demonstrated by the `getpid` benchmark:
![Figure 2](/assets/images/2023-04-28-getpid-ptrace-vs-systrap-unopt.svg "Getpid benchmark: ptrace vs. Systrap."){:width="100%"}
![Figure 2](/assets/images/2023-04-28-getpid-ptrace-vs-systrap-unoptimized.svg "Getpid benchmark: ptrace vs. Systrap."){:width="100%"}
Can we make it even faster? Recall what the main purpose of our signal handler
is: to send a request to the sentry via shared memory. To do that, the sandboxed