From: Tejun Heo <tj@kernel.org>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: linux-kernel@vger.kernel.org, dhowells@redhat.com,
sfrench@samba.org, anton@samba.org, airlied@linux.ie,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 5/7] gfs2: use workqueue instead of slow-work
Date: Fri, 23 Jul 2010 13:13:19 +0200 [thread overview]
Message-ID: <4C49794F.6010400@kernel.org> (raw)
In-Reply-To: <1279880457.2465.15.camel@localhost>
On 07/23/2010 12:20 PM, Steven Whitehouse wrote:
> Hi,
>
> On Tue, 2010-07-20 at 22:35 +0200, Tejun Heo wrote:
>> Workqueue can now handle high concurrency. Convert gfs to use
>> workqueue instead of slow-work.
>>
>> * Steven pointed out that recovery path might be run from allocation
>> path and thus requires forward progress guarantee without memory
>> allocation. Create and use gfs_recovery_wq with rescuer. Please
>> note that forward progress wasn't guaranteed with slow-work.
>>
>> * Updated to use non-reentrant workqueue.
>>
>> Signed-off-by: Tejun Heo <tj@kernel.org>
>> Cc: Steven Whitehouse <swhiteho@redhat.com>
> Acked-by: Steven Whitehouse <swhiteho@redhat.com>
>
> I'm assuming that you'll push this along with the workqueue changes?
> Probably easier than pushing it through my tree,
Yeah, I'll route this through the wq tree with all other workqueue
related changes.
Thank you.
--
tejun
WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: sfrench@samba.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, dhowells@redhat.com,
anton@samba.org
Subject: Re: [PATCH 5/7] gfs2: use workqueue instead of slow-work
Date: Fri, 23 Jul 2010 13:13:19 +0200 [thread overview]
Message-ID: <4C49794F.6010400@kernel.org> (raw)
In-Reply-To: <1279880457.2465.15.camel@localhost>
On 07/23/2010 12:20 PM, Steven Whitehouse wrote:
> Hi,
>
> On Tue, 2010-07-20 at 22:35 +0200, Tejun Heo wrote:
>> Workqueue can now handle high concurrency. Convert gfs to use
>> workqueue instead of slow-work.
>>
>> * Steven pointed out that recovery path might be run from allocation
>> path and thus requires forward progress guarantee without memory
>> allocation. Create and use gfs_recovery_wq with rescuer. Please
>> note that forward progress wasn't guaranteed with slow-work.
>>
>> * Updated to use non-reentrant workqueue.
>>
>> Signed-off-by: Tejun Heo <tj@kernel.org>
>> Cc: Steven Whitehouse <swhiteho@redhat.com>
> Acked-by: Steven Whitehouse <swhiteho@redhat.com>
>
> I'm assuming that you'll push this along with the workqueue changes?
> Probably easier than pushing it through my tree,
Yeah, I'll route this through the wq tree with all other workqueue
related changes.
Thank you.
--
tejun
next prev parent reply other threads:[~2010-07-23 11:13 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 [this message]
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
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=4C49794F.6010400@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.