All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, dhowells@redhat.com,
	sfrench@samba.org, anton@samba.org, swhiteho@redhat.com,
	airlied@linux.ie, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 6/7] drm: use workqueue instead of slow-work
Date: Thu, 22 Jul 2010 22:45:30 +0200	[thread overview]
Message-ID: <4C48ADEA.8060009@kernel.org> (raw)
In-Reply-To: <1279658102-20069-7-git-send-email-tj@kernel.org>

On 07/20/2010 10:35 PM, Tejun Heo wrote:
> Workqueue can now handle high concurrency.  Convert drm_crtc_helper to
> use system_nrt_wq instead of slow-work.  The conversion is mostly
> straight forward.  One difference is that drm_helper_hpd_irq_event()
> no longer blocks and can be called from any context.
> 
> Signed-off-by: Tejun Heo <tj@kernel.org>
> Cc: David Airlie <airlied@linux.ie>

David, can you please review the change?

Thanks.

-- 
tejun

WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: Tejun Heo <tj@kernel.org>
Cc: sfrench@samba.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, dhowells@redhat.com,
	anton@samba.org, swhiteho@redhat.com
Subject: Re: [PATCH 6/7] drm: use workqueue instead of slow-work
Date: Thu, 22 Jul 2010 22:45:30 +0200	[thread overview]
Message-ID: <4C48ADEA.8060009@kernel.org> (raw)
In-Reply-To: <1279658102-20069-7-git-send-email-tj@kernel.org>

On 07/20/2010 10:35 PM, Tejun Heo wrote:
> Workqueue can now handle high concurrency.  Convert drm_crtc_helper to
> use system_nrt_wq instead of slow-work.  The conversion is mostly
> straight forward.  One difference is that drm_helper_hpd_irq_event()
> no longer blocks and can be called from any context.
> 
> Signed-off-by: Tejun Heo <tj@kernel.org>
> Cc: David Airlie <airlied@linux.ie>

David, can you please review the change?

Thanks.

-- 
tejun

  reply	other threads:[~2010-07-22 20:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 20:34 [PATCHSET wq#for-next] workqueue: replace slow-work with workqueue Tejun Heo
2010-07-20 20:34 ` [PATCH 1/7] fscache: convert object to use workqueue instead of slow-work Tejun Heo
2010-07-20 20:34 ` [PATCH 2/7] fscache: convert operation " Tejun Heo
2010-07-20 20:34 ` [PATCH 3/7] fscache: drop references to slow-work Tejun Heo
2010-07-20 20:34 ` [PATCH 4/7] cifs: use workqueue instead of slow-work Tejun Heo
2010-07-21 15:46   ` Steve French
2010-07-20 20:35 ` [PATCH 5/7] gfs2: " Tejun Heo
2010-07-22 20:45   ` Tejun Heo
2010-07-22 20:45     ` Tejun Heo
2010-07-23 10:20   ` Steven Whitehouse
2010-07-23 11:13     ` Tejun Heo
2010-07-23 11:13       ` Tejun Heo
2010-07-20 20:35 ` [PATCH 6/7] drm: " Tejun Heo
2010-07-22 20:45   ` Tejun Heo [this message]
2010-07-22 20:45     ` Tejun Heo
2010-07-22 21:11     ` Dave Airlie
2010-07-22 21:11       ` Dave Airlie
2010-07-22 21:17       ` Tejun Heo
2010-07-22 21:17         ` Tejun Heo
2010-07-20 20:35 ` [PATCH 7/7] slow-work: kill it Tejun Heo
2010-07-22 21:00 ` [PATCHSET wq#for-next] workqueue: replace slow-work with workqueue Tejun Heo
2010-07-23 11:22   ` Tejun Heo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C48ADEA.8060009@kernel.org \
    --to=tj@kernel.org \
    --cc=airlied@linux.ie \
    --cc=anton@samba.org \
    --cc=dhowells@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfrench@samba.org \
    --cc=swhiteho@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.