diff options
| author | Xishi Qiu <qiuxishi@huawei.com> | 2013-11-06 13:18:21 -0800 |
|---|---|---|
| committer | Jiri Kosina <jkosina@suse.cz> | 2013-12-02 14:45:19 +0100 |
| commit | c79a8d85d7f540e9dbe3e3111c41d14395a0c9e2 (patch) | |
| tree | 198f357e8400c622c42303a663275371ba512350 /Documentation/static-keys.txt | |
| parent | 48807e17101773117e36916f767fc12018e0eb21 (diff) | |
| download | linux-c79a8d85d7f540e9dbe3e3111c41d14395a0c9e2.tar.gz linux-c79a8d85d7f540e9dbe3e3111c41d14395a0c9e2.tar.bz2 linux-c79a8d85d7f540e9dbe3e3111c41d14395a0c9e2.zip | |
doc: fix some typos in documentations
Fix some typos in five documentations, no functional change.
Signed-off-by: Xishi Qiu <qiuxishi@huawei.com>
Acked-by: Rob Landley <rob@landley.net>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'Documentation/static-keys.txt')
| -rw-r--r-- | Documentation/static-keys.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/static-keys.txt b/Documentation/static-keys.txt index 9f5263d3152c..c4407a41b0fc 100644 --- a/Documentation/static-keys.txt +++ b/Documentation/static-keys.txt @@ -116,7 +116,7 @@ The branch(es) can then be switched via: static_key_slow_dec(&key); Thus, 'static_key_slow_inc()' means 'make the branch true', and -'static_key_slow_dec()' means 'make the the branch false' with appropriate +'static_key_slow_dec()' means 'make the branch false' with appropriate reference counting. For example, if the key is initialized true, a static_key_slow_dec(), will switch the branch to false. And a subsequent static_key_slow_inc(), will change the branch back to true. Likewise, if the @@ -236,7 +236,7 @@ label case adds: If we then include the padding bytes, the jump label code saves, 16 total bytes of instruction memory for this small function. In this case the non-jump label -function is 80 bytes long. Thus, we have have saved 20% of the instruction +function is 80 bytes long. Thus, we have saved 20% of the instruction footprint. We can in fact improve this even further, since the 5-byte no-op really can be a 2-byte no-op since we can reach the branch with a 2-byte jmp. However, we have not yet implemented optimal no-op sizes (they are currently |