[<prev] [next>] [day] [month] [year] [list]
Message-id: <20180221152125.5490-1-sxwjean@me.com>
Date: Wed, 21 Feb 2018 23:21:25 +0800
From: Xiongwei Song <sxwjean@...com>
To: corbet@....net
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
sxwjean@...il.com
Subject: [PATCH] tracing: Remove redundant subject
There are two consecutive 'we' to represent subject, remove one of the two.
Signed-off-by: Xiongwei Song <sxwjean@...com>
---
Documentation/trace/events.txt | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/trace/events.txt b/Documentation/trace/events.txt
index 1d486660b40f..813b140cfe2c 100644
--- a/Documentation/trace/events.txt
+++ b/Documentation/trace/events.txt
@@ -878,10 +878,10 @@ The following commands are supported:
Because the default sort key above is 'hitcount', the above shows a
the list of call_sites by increasing hitcount, so that at the bottom
we see the functions that made the most kmalloc calls during the
- run. If instead we we wanted to see the top kmalloc callers in
- terms of the number of bytes requested rather than the number of
- calls, and we wanted the top caller to appear at the top, we can use
- the 'sort' parameter, along with the 'descending' modifier:
+ run. If instead we wanted to see the top kmalloc callers in terms
+ of the number of bytes requested rather than the number of calls,
+ and we wanted the top caller to appear at the top, we can use the
+ 'sort' parameter, along with the 'descending' modifier:
# echo 'hist:key=call_site.sym:val=bytes_req:sort=bytes_req.descending' > \
/sys/kernel/debug/tracing/events/kmem/kmalloc/trigger
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists