linux-kernel - Re: [PATCH] [AIO] remove unused aio_run

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060801072731.GA20484@in.ibm.com>
Date:	Tue, 1 Aug 2006 12:57:31 +0530
From:	Suparna Bhattacharya <suparna@...ibm.com>
To:	Zach Brown <zach.brown@...cle.com>
Cc:	linux-aio@...ck.org, linux-kernel@...r.kernel.org,
	Benjamin LaHaise <bcrl@...ck.org>,
	Andrew Morton <akpm@...l.org>, mason@...e.com
Subject: Re: [PATCH] [AIO] remove unused aio_run_iocbs()

On Mon, Jul 31, 2006 at 03:12:29PM -0700, Zach Brown wrote:
> [AIO] remove unused aio_run_iocbs()
> 
> Nothing is calling the aio_run_iocbs() variant of *aio_run_*iocb*().  Let's try
> and make life just a little less complicated by getting rid of it.

Chris Mason's aio pipe patches used these to reduce the large
number of context switches he was observing when running pipetest.
Of course aio pipe support hasn't been merged into mainline so far, and hence
you could argue that we put these back in if/when we hit that problem. But why
not just put in a comment there for now to ease the confusion ... generally
I'd rather go a little slow in removing apparently unused code at this
point when we are churning things up again.

Regards
Suparna

> 
> Signed-off-by: Zach Brown <zach.brown@...cle.com>
> ---
> 
>  fs/aio.c |   21 ++-------------------
>  1 file changed, 2 insertions(+), 19 deletions(-)
> 
> Index: 2.6.18-rc3-trivialaio/fs/aio.c
> ===================================================================
> --- 2.6.18-rc3-trivialaio.orig/fs/aio.c
> +++ 2.6.18-rc3-trivialaio/fs/aio.c
> @@ -814,30 +814,13 @@ static void aio_queue_work(struct kioctx
>  	queue_delayed_work(aio_wq, &ctx->wq, timeout);
>  }
>  
> -
>  /*
> - * aio_run_iocbs:
> + * aio_run_all_iocbs:
>   * 	Process all pending retries queued on the ioctx
> - * 	run list.
> + * 	run list.  It will retry until the list stays empty.
>   * 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
> - */
>  static inline void aio_run_all_iocbs(struct kioctx *ctx)
>  {
>  	spin_lock_irq(&ctx->ctx_lock);
> 
> --
> To unsubscribe, send a message with 'unsubscribe linux-aio' in
> the body to majordomo@...ck.org.  For more info on Linux AIO,
> see: http://www.kvack.org/aio/
> Don't email: <a href=mailto:"aart@...ck.org">aart@...ck.org</a>

-- 
Suparna Bhattacharya (suparna@...ibm.com)
Linux Technology Center
IBM Software Lab, India

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/