summaryrefslogtreecommitdiff
path: root/btt/trace_queue.c
diff options
context:
space:
mode:
authorAlan D. Brunelle <Alan.Brunelle@hp.com>2007-04-13 20:12:47 +0200
committerJens Axboe <jens.axboe@oracle.com>2007-04-13 20:12:47 +0200
commitc8b0b334cc1028ad8aa5407667233747af96a942 (patch)
tree07144255c7a332021e5dcdccf1cdda366811675a /btt/trace_queue.c
parent425c69552d4fbf7705c74aef4761324ed641cb28 (diff)
downloadblktrace-c8b0b334cc1028ad8aa5407667233747af96a942.tar.gz
blktrace-c8b0b334cc1028ad8aa5407667233747af96a942.tar.bz2
A couple of weeks ago Ming Zhang had noted that btt was using tremendous
amounts of memory to accomplish a run. After looking at the code, and doing some testing, I determined the cause - please find a patch to the latest tree that seems to fix the problem for me... Signed-off-by: Alan D. Brunelle <Alan.Brunelle@hp.com> Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
Diffstat (limited to 'btt/trace_queue.c')
-rw-r--r--btt/trace_queue.c8
1 files changed, 4 insertions, 4 deletions
diff --git a/btt/trace_queue.c b/btt/trace_queue.c
index ea285e3..ad5e30c 100644
--- a/btt/trace_queue.c
+++ b/btt/trace_queue.c
@@ -28,20 +28,20 @@ static inline void __update_q2c(struct io *q_iop, struct io *c_iop)
latency_q2c(q_iop->dip, q_iop->t.time, q2c);
}
-void run_queue(struct io *q_iop, struct io *c_iop, struct list_head *rmhd)
+void run_queue(struct io *q_iop, __attribute__((__unused__))struct io *u_iop,
+ struct io *c_iop)
{
struct bilink *blp;
struct io *a_iop = bilink_first_down(q_iop, &blp);
if (a_iop) {
- run_remap(a_iop, c_iop, rmhd);
+ run_remap(a_iop, q_iop, c_iop);
biunlink(blp);
}
__update_q2c(q_iop, c_iop);
dump_iop(q_iop, 0);
-
- list_add_tail(&q_iop->f_head, rmhd);
+ add_rmhd(q_iop);
}
int ready_queue(struct io *q_iop, struct io *c_iop)