[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <x49k50yjzdd.fsf@segfault.boston.devel.redhat.com>
Date: Thu, 20 Aug 2009 11:09:34 -0400
From: Jeff Moyer <jmoyer@...hat.com>
To: Jens Axboe <jens.axboe@...cle.com>
Cc: linux-kernel@...r.kernel.org, jeff@...zik.org,
benh@...nel.crashing.org, htejun@...il.com, bzolnier@...il.com,
alan@...rguk.ukuu.org.uk, zach.brown@...cle.com
Subject: Re: [PATCH 5/6] aio: use lazy workqueues
Jens Axboe <jens.axboe@...cle.com> writes:
> Signed-off-by: Jens Axboe <jens.axboe@...cle.com>
> ---
> fs/aio.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/fs/aio.c b/fs/aio.c
> index d065b2c..4103b59 100644
> --- a/fs/aio.c
> +++ b/fs/aio.c
> @@ -72,7 +72,7 @@ static int __init aio_setup(void)
> kiocb_cachep = KMEM_CACHE(kiocb, SLAB_HWCACHE_ALIGN|SLAB_PANIC);
> kioctx_cachep = KMEM_CACHE(kioctx,SLAB_HWCACHE_ALIGN|SLAB_PANIC);
>
> - aio_wq = create_workqueue("aio");
> + aio_wq = create_lazy_workqueue("aio");
>
> pr_debug("aio_setup: sizeof(struct page) = %d\n", (int)sizeof(struct page));
So far as I can tell, the aio workqueue isn't used for much these days.
We could probably get away with switching to keventd. Zach, isn't
someone working on a patch to get rid of all of the -EIOCBRETRY
infrastructure? That patch would probably make things clearer in this
area.
Cheers,
Jeff
--
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/
Powered by blists - more mailing lists