...and the last images fixed

Patch 7: SysCall/, Theory/ and Timers/
yakuizhao · Oct 10, 2019 · e67179a · e67179a
1 parent fd8281d
commit e67179a
Show file tree

Hide file tree

Showing 8 changed files with 4 additions and 4 deletions.
diff --git a/SysCall/images/ls_shell.png b/SysCall/images/ls_shell.png
diff --git a/SysCall/linux-syscall-4.md b/SysCall/linux-syscall-4.md
@@ -20,7 +20,7 @@ There are many different ways to launch an application from a user perspective.
 
 In this part we will consider the way when we just launch an application from the shell. As you know, the standard way to launch an application from shell is the following: We just launch a [terminal emulator](https://en.wikipedia.org/wiki/Terminal_emulator) application and just write the name of the program and pass or not arguments to our program, for example:
 
-![ls shell](http://i66.tinypic.com/214w6so.jpg)
+![ls shell](images/ls_shell.png)
 
 Let's consider what does occur when we launch an application from the shell, what does shell do when we write program name, what does Linux kernel do etc. But before we will start to consider these interesting things, I want to warn that this book is about the Linux kernel. That's why we will see Linux kernel insides related stuff mostly in this part. We will not consider in details what does shell do, we will not consider complex cases, for example subshells etc.
 

diff --git a/Theory/images/4_level_paging.png b/Theory/images/4_level_paging.png
diff --git a/Theory/linux-theory-1.md b/Theory/linux-theory-1.md
@@ -93,7 +93,7 @@ The linear address translation is following:
 
 schematically, we can imagine it like this:
 
-![4-level paging](http://oi58.tinypic.com/207mb0x.jpg)
+![4-level paging](images/4_level_paging.png)
 
 Every access to a linear address is either a supervisor-mode access or a user-mode access. This access is determined by the `CPL` (current privilege level). If `CPL < 3` it is a supervisor mode access level, otherwise it is a user mode access level. For example, the top level page table entry contains access bits and has the following structure (See [arch/x86/include/asm/pgtable_types.h](https://github.com/torvalds/linux/blob/16f73eb02d7e1765ccab3d2018e0bd98eb93d973/arch/x86/include/asm/pgtable_types.h) for the bit offset definitions):
 

diff --git a/Timers/images/HZ.png b/Timers/images/HZ.png
diff --git a/Timers/images/base_small.png b/Timers/images/base_small.png
diff --git a/Timers/linux-timers-1.md b/Timers/linux-timers-1.md
@@ -259,7 +259,7 @@ The `jiffies` clock source uses the `NSEC_PER_JIFFY` multiplier conversion to sp
 
 Where `CONFIG_HZ` can be one of the following values:
 
-![HZ](http://i63.tinypic.com/v8d6ph.png)
+![HZ](images/HZ.png)
 
 This means that in our case the timer interrupt frequency is `250 HZ` or occurs `250` times per second or one timer interrupt each `4ms`.
 

diff --git a/Timers/linux-timers-4.md b/Timers/linux-timers-4.md
@@ -117,7 +117,7 @@ struct tvec_root {
 
 type. Note that the value of the `TVR_SIZE` depends on the `CONFIG_BASE_SMALL` kernel configuration option:
 
-![base small](http://i68.tinypic.com/aylkt2.png)
+![base small](images/base_small.png)
 
 that reduces size of the kernel data structures if disabled. The `v1` is array that may contain `64` or `256` elements where an each element represents a dynamic timer that will decay within the next `255` system timer interrupts. Next three fields: `tv2`, `tv3` and `tv4` are lists with dynamic timers too, but they store dynamic timers which will decay the next `2^14 - 1`, `2^20 - 1` and `2^26` respectively. The last `tv5` field represents list which stores dynamic timers with a large expiring period.