[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1278349860.2229.9.camel@localhost>
Date: Mon, 05 Jul 2010 13:11:00 -0400
From: Andy Walls <awalls@...metrocast.net>
To: Tejun Heo <tj@...nel.org>
Cc: torvalds@...ux-foundation.org, mingo@...e.hu,
linux-kernel@...r.kernel.org, jeff@...zik.org,
akpm@...ux-foundation.org, rusty@...tcorp.com.au,
cl@...ux-foundation.org, dhowells@...hat.com,
arjan@...ux.intel.com, oleg@...hat.com, axboe@...nel.dk,
fweisbec@...il.com, dwalker@...eaurora.org,
stefanr@...6.in-berlin.de, florian@...kler.org,
andi@...stfloor.org, mst@...hat.com, randy.dunlap@...cle.com,
ivtv-devel@...vdriver.org, linux-media@...r.kernel.org
Subject: Re: [PATCH 02/35] ivtv: use kthread_worker instead of workqueue
On Mon, 2010-06-28 at 23:03 +0200, Tejun Heo wrote:
> Upcoming workqueue updates will no longer guarantee fixed workqueue to
> worker kthread association, so giving RT priority to the irq worker
> won't work. Use kthread_worker which guarantees specific kthread
> association instead. This also makes setting the priority cleaner.
>
> Signed-off-by: Tejun Heo <tj@...nel.org>
> Cc: Andy Walls <awalls@...metrocast.net>
> Cc: Andrew Morton <akpm@...ux-foundation.org>
> Cc: ivtv-devel@...vdriver.org
> Cc: linux-media@...r.kernel.org
Assuming the new kthread_worker implementation is OK, this change for
ivtv looks good.
Reviewed-by: Andy Walls <awalls@...metrocast.net>
Acked-by: Andy Walls <awalls@...metrocast.net>
Regards,
Andy
> drivers/media/video/ivtv/ivtv-driver.c | 26 ++++++++++++++++----------
> drivers/media/video/ivtv/ivtv-driver.h | 8 ++++----
> drivers/media/video/ivtv/ivtv-irq.c | 15 +++------------
> drivers/media/video/ivtv/ivtv-irq.h | 2 +-
> 4 files changed, 24 insertions(+), 27 deletions(-)
>
> diff --git a/drivers/media/video/ivtv/ivtv-driver.c b/drivers/media/video/ivtv/ivtv-driver.c
> index 1b79475..49e0b1c 100644
> --- a/drivers/media/video/ivtv/ivtv-driver.c
> +++ b/drivers/media/video/ivtv/ivtv-driver.c
--
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