サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
Switch 2
blog.packagecloud.io
TL;DR This blog post explains how ltrace works, internally. This is a great companion post to our previous blog post which describes strace internals. We’ll begin by examining the difference between ltrace and strace. Next, we’ll move on to examining the ptrace system call and the ways in which ltrace uses it to get information about library calls being made in a running process. ltrace vs strace
TL;DR This blog post dives into an interesting finding: two frequently used system calls (gettimeofday, clock_gettime) are much slower on AWS EC2. Linux provides a mechanism for speeding up those two frequently used system calls by implementing the system call code in userland and avoiding the switch to the kernel entirely. This is done via a virtual shared library provided by the kernel that is m
How setting the TZ environment variable avoids thousands of system calls TL;DR This blog post explains how setting an environment variable can save thousands (or in some cases, tens of thousands) of unnecessary system calls that can be generated by glibc over small periods of time. This has been tested on Ubuntu Precise (12.04) and Ubuntu Xenial (16.04). It likely applies to other flavors of Linux
Monitoring and Tuning the Linux Networking Stack: Sending Data TL;DR This blog post explains how computers running the Linux kernel send packets, as well as how to monitor and tune each component of the networking stack as packets flow from user programs to network hardware. This post forms a pair with our previous post Monitoring and Tuning the Linux Networking Stack: Receiving Data. It is imposs
TL;DR strace traces system calls and signals and is an invaluable tool for gathering context when debugging. This cheat sheet will show a few useful ways of using strace, how to filter the output, and summarize some of the more useful commands line arguments that strace accepts. strace PTRACE_TRACEME EPERM (Operation not permitted) You should run strace as root. If you get this message when runnin
TL;DR This blog post explains how strace works, internally. We’ll examine the ptrace system call, which strace relies on, at the API layer and internally to understand how exactly strace can get information about the system calls being made in a running process. ptrace ptrace is a system call which a program can use to: trace system calls read and write memory and registers manipulate signal deliv
Monitoring and Tuning the Linux Networking Stack: Receiving Data TL;DR This blog post explains how computers running the Linux kernel receive packets, as well as how to monitor and tune each component of the networking stack as packets flow from the network toward userland programs. UPDATE We’ve released the counterpart to this post: Monitoring and Tuning the Linux Networking Stack: Sending Data.
TL;DR This blog post explains how Linux programs call functions in the Linux kernel. It will outline several different methods of making systems calls, how to handcraft your own assembly to make system calls (examples included), kernel entry points into system calls, kernel exit points from system calls, glibc wrappers, bugs, and much, much more. Here is a summary of the topics this blog post will
このページを最初にブックマークしてみませんか?
『Page Packagecloud Blog』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く