3rd-party/LKMPG
1
0
Fork 0
mirror of https://github.com/bashrc/LKMPG.git synced 2018-06-11 03:06:54 +02:00
Code Issues Releases Wiki Activity

dot diagram

Browse Source
This commit is contained in:
Bob Mottram
2016-03-09 15:47:16 +00:00
parent 04b6165f97
commit 628b770c72
4 changed files with 29 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
LKMPG-3.16.html
View File

@@ -3,7 +3,7 @@
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!-- 2016-03-09 Wed 14:54 -->
<!-- 2016-03-09 Wed 15:43 -->
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>The Linux Kernel Module Programming Guide</title>
@@ -2423,23 +2423,23 @@ BE CARREFUL: when a sequence is finished, another one starts. That means that at
<div id="outline-container-orgheadline54" class="outline-4">
<h4 id="orgheadline54">Figure: How seq_file works</h4>
<div class="outline-text-4" id="text-orgheadline54">
<div class="figure">
<p><img src="img/seq_file.png" alt="seq_file.png" />
</p>
</div>
<table border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
<colgroup>
<col class="org-left" />
</colgroup>
<thead>
<tr>
<th scope="col" class="org-left"><img src="./seq_file.jpg" alt="seq_file.jpg" /></th>
</tr>
</thead>
<tbody>
<tr>
<td class="org-left">Seq_file provides basic functions for file_operations, as seq_read, seq_lseek, and some others. But nothing to write in the /proc file. Of course, you can still use the same way as in the previous example.</td>
</tr>
</tbody>
</table>
<p>
Seq_file provides basic functions for file_operations, as seq_read, seq_lseek, and some others. But nothing to write in the /proc file. Of course, you can still use the same way as in the previous example.
</p>
</div>
</div>

22
LKMPG-3.16.org
View File

@@ -1490,9 +1490,25 @@ BE CARREFUL: when a sequence is finished, another one starts. That means that at
*** Figure: How seq_file works
| [[./seq_file.jpg]] |
|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Seq_file provides basic functions for file_operations, as seq_read, seq_lseek, and some others. But nothing to write in the /proc file. Of course, you can still use the same way as in the previous example. |
#+BEGIN_SRC dot :file img/seq_file.png
digraph seq_file {
yesnull [label="Yes" border=0];
returnnull1 [label="return is NULL?" shape=diamond];
returnnull2 [label="return is NULL?" shape=diamond];
start [label="start() treatment" shape=box];
next [label="next() treatment" shape=box];
stop [label="stop() treatment" shape=box];
start -> returnnull1;
returnnull1 -> next [label="No"];
returnnull1 -> yesnull;
next -> returnnull2;
returnnull2 -> next [label="No"];
returnnull2 -> stop [label="Yes"];
stop -> start;
}
#+END_SRC
|
Seq_file provides basic functions for file_operations, as seq_read, seq_lseek, and some others. But nothing to write in the /proc file. Of course, you can still use the same way as in the previous example.
*** Example: procfs4.c
#+BEGIN_SRC c

BIN
img/seq_file.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 24 KiB

BIN
seq_file.jpg
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 38 KiB