Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756689Ab0GWKQW (ORCPT ); Fri, 23 Jul 2010 06:16:22 -0400 Received: from mx1.redhat.com ([209.132.183.28]:23334 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756462Ab0GWKQS (ORCPT ); Fri, 23 Jul 2010 06:16:18 -0400 Subject: Re: [PATCH 5/7] gfs2: use workqueue instead of slow-work From: Steven Whitehouse To: Tejun Heo Cc: linux-kernel@vger.kernel.org, dhowells@redhat.com, sfrench@samba.org, anton@samba.org, airlied@linux.ie, dri-devel@lists.freedesktop.org In-Reply-To: <1279658102-20069-6-git-send-email-tj@kernel.org> References: <1279658102-20069-1-git-send-email-tj@kernel.org> <1279658102-20069-6-git-send-email-tj@kernel.org> Content-Type: text/plain; charset="UTF-8" Organization: Red Hat UK Ltd Date: Fri, 23 Jul 2010 11:20:57 +0100 Message-ID: <1279880457.2465.15.camel@localhost> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 997 Lines: 28 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 > Cc: Steven Whitehouse Acked-by: Steven Whitehouse I'm assuming that you'll push this along with the workqueue changes? Probably easier than pushing it through my tree, Steve. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/