linux-kernel - Re: [RFC] memory hotremove patch take 2 [02/10] (make page unused)

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 10 May 2007 11:04:37 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Yasunori Goto <y-goto@...fujitsu.com>
cc:	Linux Kernel ML <linux-kernel@...r.kernel.org>,
	linux-mm <linux-mm@...ck.org>, Andrew Morton <akpm@...l.org>,
	Mel Gorman <mel@....ul.ie>
Subject: Re: [RFC] memory hotremove patch take 2 [02/10] (make page unused)

On Wed, 9 May 2007, Yasunori Goto wrote:

> This patch is for supporting making page unused.
> 
> Isolate pages by capturing freed pages before inserting free_area[],
> buddy allocator.
> If you have an idea for avoiding spin_lock(), please advise me.

Using the zone lock instead may avoid to introduce another lock? Or is the 
new lock here for performance reasons?

Isnt it possible to just add another flavor of pages like what Mel has 
been doing with reclaimable and movable? I.e. add another category of free 
pages to Mel's scheme called isolated and use Mel's function to move stuff 
over there?

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