projects / blktrace.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 71d5d4c) | patch
[PATCH] kernel: put back old syncronization
authorJens Axboe <axboe@suse.de>
Sun, 25 Sep 2005 12:31:24 +0000 (14:31 +0200)
committerJens Axboe <axboe@suse.de>
Sun, 25 Sep 2005 12:31:24 +0000 (14:31 +0200)
commit407ab742c5c8e3b90b12d5ba45361bef4b06d2a0
tree295f6a67fe8d035f6fb2c1741cdda43ce378c18atree | snapshot
parent71d5d4c9156c5946e76fe9909b234e9da64a8341commit | diff
[PATCH] kernel: put back old syncronization

It's actually the best - keep the trace on the stack, so multiple
invocations from the same CPU (ie from process and irq context at
the same time) get their own 't', and keep the local irq disable
to prevent interleaving of trace and PDU with other contexts.
kernel/blk-trace-2.6.14-rc2-git-I0 [deleted file] blob | blame | history
kernel/blk-trace-2.6.14-rc2-git-J0 [new file with mode: 0644] blob
Block queue io tracer