diff options
Diffstat (limited to 'Documentation/filesystems/proc.txt')
-rw-r--r-- | Documentation/filesystems/proc.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt index 770700317c2c..f6b1b5fca1df 100644 --- a/Documentation/filesystems/proc.txt +++ b/Documentation/filesystems/proc.txt | |||
@@ -965,7 +965,7 @@ your system and how much traffic was routed over those devices: | |||
965 | ...] 1375103 17405 0 0 0 0 0 0 | 965 | ...] 1375103 17405 0 0 0 0 0 0 |
966 | ...] 1703981 5535 0 0 0 3 0 0 | 966 | ...] 1703981 5535 0 0 0 3 0 0 |
967 | 967 | ||
968 | In addition, each Channel Bond interface has it's own directory. For | 968 | In addition, each Channel Bond interface has its own directory. For |
969 | example, the bond0 device will have a directory called /proc/net/bond0/. | 969 | example, the bond0 device will have a directory called /proc/net/bond0/. |
970 | It will contain information that is specific to that bond, such as the | 970 | It will contain information that is specific to that bond, such as the |
971 | current slaves of the bond, the link status of the slaves, and how | 971 | current slaves of the bond, the link status of the slaves, and how |
@@ -1362,7 +1362,7 @@ been accounted as having caused 1MB of write. | |||
1362 | In other words: The number of bytes which this process caused to not happen, | 1362 | In other words: The number of bytes which this process caused to not happen, |
1363 | by truncating pagecache. A task can cause "negative" IO too. If this task | 1363 | by truncating pagecache. A task can cause "negative" IO too. If this task |
1364 | truncates some dirty pagecache, some IO which another task has been accounted | 1364 | truncates some dirty pagecache, some IO which another task has been accounted |
1365 | for (in it's write_bytes) will not be happening. We _could_ just subtract that | 1365 | for (in its write_bytes) will not be happening. We _could_ just subtract that |
1366 | from the truncating task's write_bytes, but there is information loss in doing | 1366 | from the truncating task's write_bytes, but there is information loss in doing |
1367 | that. | 1367 | that. |
1368 | 1368 | ||