summaryrefslogtreecommitdiff
path: root/ioshark/README
diff options
context:
space:
mode:
authorMohan Srinivasan <srmohan@google.com>2017-03-09 11:24:38 -0800
committerMohan Srinivasan <srmohan@google.com>2017-03-15 12:14:10 -0700
commit9d00a124c5591198264ffedf0ba4c73bddfc346f (patch)
tree1883df6e56f077ce40ae6ce7a152671a749b96af /ioshark/README
parent7db706e162e76764ebca62c4f2808ac6e0940b52 (diff)
downloadextras-9d00a124c5591198264ffedf0ba4c73bddfc346f.tar.gz
IOshark support to parse Linux filesystem ftraces.
IOshark support to input filesystem ftracepooints (readpage(s)) to capture and replay mmap'ed IO (which aren't captured by strace). The new script collect-straces-ftraces.sh enables the necessary tracepoints, and collects ftraces and straces compiles these into intermediate bytecodes which ioshark_bench can then execute. Test: Generate several monkey based workloads, and use the script mentioned above to generate bytecodes and feed those into ioshark_bench. Change-Id: Iae57f5fdcdce0fedfd85c8d64ee006cc8b5b470d Signed-off-by: Mohan Srinivasan <srmohan@google.com>
Diffstat (limited to 'ioshark/README')
-rw-r--r--ioshark/README13
1 files changed, 8 insertions, 5 deletions
diff --git a/ioshark/README b/ioshark/README
index ee2f426b..0c50fec3 100644
--- a/ioshark/README
+++ b/ioshark/README
@@ -3,11 +3,11 @@ can find more documentation on IOshark at :
https://docs.google.com/a/google.com/document/d/1Bhq7iNPVc_JzwRrkmZqcPjMvWgpHX0r3Ncq-ZsRNOBA/edit?usp=sharing
The short summary of what IOshark is : IOshark has 2 components, one
-is a strace compiler that takes straces fed into it and compiles this
-into bytecodes (stored in *.wl files). The compiler runs on a Linux
-host. The second component (which runs on the device) is the tester
-that takes as input the bytecode files (*.wl files) and executes them
-on the device.
+is a strace+ftrace compiler that takes straces and select ftraces fed
+into it and compiles this into bytecodes (stored in *.wl files). The
+compiler runs on a Linux host. The second component (which runs on the
+device) is the tester that takes as input the bytecode files (*.wl
+files) and executes them on the device.
How to Run :
----------
@@ -25,3 +25,6 @@ seen in the original straces.
-t <N> : Limit to N threads. By default (without this option), IOshark
will launch as many threads as there are input files, so 1 thread/file.
-v : verbose. Chatty mode.
+-s : One line summary.
+-q : Don't create the files in read-only partitions like /system and
+/vendor. Instead do reads on those files.