How to get the blktrace tool to show the D - issued action -


this question blktrace tool. on several unbuntu 3.16.0 machines in our lab need trace software vs device block io performance. use our custom nvme driver , standard one. here excerpt of blkparse output (with standard nvme driver):

259,0    2   189505     9.997188463  8160  q   r 126875648 + 248 [fio] 259,0    2   189506     9.997191290  8160  q   r 126875896 + 8 [fio] 259,0    2   189507     9.997215574  8160  q   r 363057152 + 248 [fio] 259,0    2   189508     9.997218444  8160  q   r 363057400 + 8 [fio] 259,0    2   189509     9.997219210  8160  c   r 216536568 + 8 [0] 259,0    2   189510     9.997220497  8160  c   r 126875896 + 8 [0] 259,0    2   189511     9.997230160  8160  c   r 363057400 + 8 [0] 259,0    2   189512     9.997248050  8160  q   r 147316736 + 248 [fio] 259,0    2   189513     9.997250930  8160  q   r 147316984 + 8 [fio] 259,0    2   189514     9.997277161     0  c   r 147316984 + 8 [0] 

this shows queued , complete actions not d - issued actions interested in. problem. need more actions (events) shown.

blktrace /dev/nvme0n1 

meanwhile, on other linux machines works, or on same machine if trace different device like

blktrace /dev/sda 

that works shown in excerpt:

  8,0   18       69    17.778827207  8538  q  ra 306186592 + 8 [ls]   8,0   18       70    17.778827767  8538  g  ra 306186592 + 8 [ls]   8,0   18       71    17.778828037  8538    r 306186592 + 8 [ls]   8,0   18       72    17.778828284  8538  d   r 306186592 + 8 [ls]   8,0   18       73    17.778832181  8538   ra 306186600 + 8 <- (8,1) 306184552   8,0   18       74    17.778832397  8538  q  ra 306186600 + 8 [ls]   8,0   18       75    17.778832951  8538  g  ra 306186600 + 8 [ls]   8,0   18       76    17.778833221  8538    r 306186600 + 8 [ls]   8,0   18       77    17.778833441  8538  d   r 306186600 + 8 [ls]   8,0   18       78    17.778837161  8538   ra 306186608 + 8 <- (8,1) 306184560 

this last 1 (with /dev/sda) shows different actions, great. how detailed blktrace nvme0n1 device? , why not automatically show other actions (besides q , c)?

you should able see d long nvme device has block device interface. try libaio engine in fio , run random write. make sure set noop io scheduler in /sys/block/nvme../scheduler


Comments

Popular posts from this blog

OpenCV OpenCL: Convert Mat to Bitmap in JNI Layer for Android -

android - org.xmlpull.v1.XmlPullParserException: expected: START_TAG {http://schemas.xmlsoap.org/soap/envelope/}Envelope -

python - How to remove the Xframe Options header in django? -