linux-kernel - Re: [PATCH] firewire: sbp2: parallelize login/inquiry, reconnect, and shutdown

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: <4CB490DA.8020107@kernel.org>
Date:	Tue, 12 Oct 2010 18:46:18 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
CC:	linux1394-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] firewire: sbp2: parallelize login/inquiry, reconnect,
 and shutdown

Hello,

On 10/12/2010 06:15 PM, Stefan Richter wrote:
> Tejun Hejo wrote:
>> It doesn't have to be swap.  Having a rw filesystem mounted is enough
>> to be in the memory reclaim path.
> 
> Oh, alright.
> 
> ...
>> Yes, it would definitely be better to put them in a workqueue with
>> WQ_RESCUER (or the new WQ_MEM_RECLAIM).
> 
> A pro pos WQ_MEM_RECLAIM, is wq.git#for-next stable history which I can pull
> into a topic branch at linux1394-2.6.git?  (Or I wait with this stuff until
> after .37-rc1.)

For now using WQ_RESCUER should do.  We can update it to
WQ_MEM_RECLAIM after the trees are merged (both flags have the same
meaning now so nothing would break).

Thanks.

-- 
tejun
--
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/