Browse code

fix minor docs issues

this brings back the trailing whitespace in "runmetrics",
that were there intentially to force a line-break

also removes a duplicate redirect, that was present
on two pages

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

Sebastiaan van Stijn authored on 2016/07/27 18:09:57
Showing 2 changed files
... ...
@@ -139,7 +139,7 @@ indicates the number of page faults which happened since the creation of
139 139
 the cgroup; this number can never decrease).
140 140
 
141 141
 
142
- - **cache:**
142
+ - **cache:**  
143 143
    the amount of memory used by the processes of this control group
144 144
    that can be associated precisely with a block on a block device.
145 145
    When you read from and write to files on disk, this amount will
... ...
@@ -149,16 +149,16 @@ the cgroup; this number can never decrease).
149 149
    `mmap`). It also accounts for the memory used by
150 150
    `tmpfs` mounts, though the reasons are unclear.
151 151
 
152
- - **rss:**
152
+ - **rss:**  
153 153
    the amount of memory that *doesn't* correspond to anything on disk:
154 154
    stacks, heaps, and anonymous memory maps.
155 155
 
156
- - **mapped_file:**
156
+ - **mapped_file:**  
157 157
    indicates the amount of memory mapped by the processes in the
158 158
    control group. It doesn't give you information about *how much*
159 159
    memory is used; it rather tells you *how* it is used.
160 160
 
161
- - **pgfault and pgmajfault:**
161
+ - **pgfault and pgmajfault:**  
162 162
    indicate the number of times that a process of the cgroup triggered
163 163
    a "page fault" and a "major fault", respectively. A page fault
164 164
    happens when a process accesses a part of its virtual memory space
... ...
@@ -177,10 +177,10 @@ the cgroup; this number can never decrease).
177 177
    it just has to duplicate an existing page, or allocate an empty
178 178
    page, it's a regular (or "minor") fault.
179 179
 
180
- - **swap:**
180
+ - **swap:**  
181 181
    the amount of swap currently used by the processes in this cgroup.
182 182
 
183
- - **active_anon and inactive_anon:**
183
+ - **active_anon and inactive_anon:**  
184 184
    the amount of *anonymous* memory that has been identified has
185 185
    respectively *active* and *inactive* by the kernel. "Anonymous"
186 186
    memory is the memory that is *not* linked to disk pages. In other
... ...
@@ -195,7 +195,7 @@ the cgroup; this number can never decrease).
195 195
    retagged "active". When the kernel is almost out of memory, and time
196 196
    comes to swap out to disk, the kernel will swap "inactive" pages.
197 197
 
198
- - **active_file and inactive_file:**
198
+ - **active_file and inactive_file:**  
199 199
    cache memory, with *active* and *inactive* similar to the *anon*
200 200
    memory above. The exact formula is cache = **active_file** +
201 201
    **inactive_file** + **tmpfs**. The exact rules used by the kernel
... ...
@@ -206,14 +206,14 @@ the cgroup; this number can never decrease).
206 206
    since it can be reclaimed immediately (while anonymous pages and
207 207
    dirty/modified pages have to be written to disk first).
208 208
 
209
- - **unevictable:**
209
+ - **unevictable:**  
210 210
    the amount of memory that cannot be reclaimed; generally, it will
211 211
    account for memory that has been "locked" with `mlock`.
212 212
    It is often used by crypto frameworks to make sure that
213 213
    secret keys and other sensitive material never gets swapped out to
214 214
    disk.
215 215
 
216
- - **memory and memsw limits:**
216
+ - **memory and memsw limits:**  
217 217
    These are not really metrics, but a reminder of the limits applied
218 218
    to this cgroup. The first one indicates the maximum amount of
219 219
    physical memory that can be used by the processes of this control
... ...
@@ -261,21 +261,21 @@ file in the kernel documentation, here is a short list of the most
261 261
 relevant ones:
262 262
 
263 263
 
264
- - **blkio.sectors:**
264
+ - **blkio.sectors:**  
265 265
    contain the number of 512-bytes sectors read and written by the
266 266
    processes member of the cgroup, device by device. Reads and writes
267 267
    are merged in a single counter.
268 268
 
269
- - **blkio.io_service_bytes:**
269
+ - **blkio.io_service_bytes:**  
270 270
    indicates the number of bytes read and written by the cgroup. It has
271 271
    4 counters per device, because for each device, it differentiates
272 272
    between synchronous vs. asynchronous I/O, and reads vs. writes.
273 273
 
274
- - **blkio.io_serviced:**
274
+ - **blkio.io_serviced:**  
275 275
    the number of I/O operations performed, regardless of their size. It
276 276
    also has 4 counters per device.
277 277
 
278
- - **blkio.io_queued:**
278
+ - **blkio.io_queued:**  
279 279
    indicates the number of I/O operations currently queued for this
280 280
    cgroup. In other words, if the cgroup isn't doing any I/O, this will
281 281
    be zero. Note that the opposite is not true. In other words, if
... ...
@@ -1,8 +1,5 @@
1 1
 <!--[metadata]>
2 2
 +++
3
-aliases = [
4
-"/engine/swarm/how-swarm-mode-works/"
5
-]
6 3
 title = "How services work"
7 4
 description = "How swarm mode services work"
8 5
 keywords = ["docker, container, cluster, swarm mode, node"]