Skip to contentSkip to conversation

aio: remove unused function aio_run_iocbs()

PATCH In review Nikanth Karthikesan 4 participants 5 messages Jun 26, 2008 – Jul 1, 2008

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 aio: remove unused function aio_run_iocbs()

remove unused function aio_run_iocbs()

---

fs/aio.c +0 -20
index 0fb3117..e27f611 100644
@@ -797,26 +797,6 @@ static void aio_queue_work(struct kioctx * ctx)
 	queue_delayed_work(aio_wq, &ctx->wq, timeout);
 }
 
-
-/*
- * aio_run_iocbs:
- * 	Process all pending retries queued on the ioctx
- * 	run list.
- * Assumes it is operating within the aio issuer's mm
- * context.
- */
-static inline void aio_run_iocbs(struct kioctx *ctx)
-{
-	int requeue;
-
-	spin_lock_irq(&ctx->ctx_lock);
-
-	requeue = __aio_run_iocbs(ctx);
-	spin_unlock_irq(&ctx->ctx_lock);
-	if (requeue)
-		aio_queue_work(ctx);
-}
-
 /*
  * just like aio_run_iocbs, but keeps running them until
  * the list stays empty
#2 lore raw
Quoted 7 lines · Jeff Moyer
Quoted 1 line · Nikanth Karthikesan

remove unused function aio_run_iocbs()

Seems like it's time to just get rid of it. See:
http://ussg.iu.edu/hypermail/linux/kernel/0608.0/0048.html
for an explanation of why it's still there.

Yeah, I'm still of the opinion that the cost of having to resurrect it if it's needed again isn't significant enough to keep it in the tree without callers.

- z

#3 lore raw
Quoted 4 lines · On Monday 30 June 2008 23:10:50 Zach Brown wrote:
Quoted 3 lines · Jeff Moyer
Quoted 1 line · Nikanth Karthikesan

remove unused function aio_run_iocbs()

Quoted 8 lines
Quoted 3 lines

Seems like it's time to just get rid of it. See:
http://ussg.iu.edu/hypermail/linux/kernel/0608.0/0048.html
for an explanation of why it's still there.

Yeah, I'm still of the opinion that the cost of having to resurrect it if it's needed again isn't significant enough to keep it in the tree without callers.

Can't this function be kept as part of the out-of-tree patch itself? Or is it a module that requires this symbol? I do not see a EXPORT_SYMBOL*() for this, so it cannot be a module depending on this func!?

Thanks
Nikanth Karthikesan

#4 lore raw
Quoted 3 lines · Nikanth Karthikesan

Can't this function be kept as part of the out-of-tree patch itself? Or is it a module that requires this symbol? I do not see a EXPORT_SYMBOL*() for this, so it cannot be a module depending on this func!?

Yes. There's very very few reason to keep unused functions around, and a patch that hasn't been merged forever is not one of those.

Please kill it.