linux-kernel - Re: [RFC 0/3] Recursive reclaim (on __PF

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-next>] [day] [month] [year] [list]

Message-ID: <20070918115836.1394a051@twins>
Date:	Tue, 18 Sep 2007 11:58:36 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Daniel Phillips <phillips@...nq.net>
Cc:	"Mike Snitzer" <snitzer@...il.com>,
	"Christoph Lameter" <clameter@....com>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	dkegel@...gle.com, "David Miller" <davem@...emloft.net>,
	"Nick Piggin" <npiggin@...e.de>, "Wouter Verhelst" <w@...r.be>,
	"Evgeniy Polyakov" <johnpol@....mipt.ru>
Subject: Re: [RFC 0/3] Recursive reclaim (on __PF_MEMALLOC)

On Mon, 17 Sep 2007 22:11:25 -0700 Daniel Phillips <phillips@...nq.net>
wrote:


> > I've been using Avi Kivity's patch from some time ago:
> > http://lkml.org/lkml/2004/7/26/68
> 
> Yes.  Ddsnap includes a bit of code almost identical to that, which we wrote independently.  Seems wild and crazy at first blush, doesn't it? But this approach has proved robust in practice, and is to my mind, obviously correct.

I'm so not liking this :-(

Can't we just run the user-space part as mlockall and extend netlink
to work with PF_MEMALLOC where needed?

I did something like that for iSCSI.
-
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/