linux-kernel - Re: [PATCH 5/7] gfs2: use workqueue instead of slow-work

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1279880457.2465.15.camel@localhost>
Date:	Fri, 23 Jul 2010 11:20:57 +0100
From:	Steven Whitehouse <swhiteho@...hat.com>
To:	Tejun Heo <tj@...nel.org>
Cc:	linux-kernel@...r.kernel.org, dhowells@...hat.com,
	sfrench@...ba.org, anton@...ba.org, airlied@...ux.ie,
	dri-devel@...ts.freedesktop.org
Subject: Re: [PATCH 5/7] gfs2: use workqueue instead of slow-work

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@...nel.org>
> Cc: Steven Whitehouse <swhiteho@...hat.com>
Acked-by: Steven Whitehouse <swhiteho@...hat.com>

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/