linux-kernel - Re: [PATCH v2 00/10] evacuate struct page from the block layer, introduce __pfn

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: <20150507195313.GA23597@gmail.com>
Date:	Thu, 7 May 2015 21:53:13 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Jerome Glisse <j.glisse@...il.com>
Cc:	Dave Hansen <dave.hansen@...ux.intel.com>,
	Dan Williams <dan.j.williams@...el.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Boaz Harrosh <boaz@...xistor.com>, Jan Kara <jack@...e.cz>,
	Mike Snitzer <snitzer@...hat.com>, Neil Brown <neilb@...e.de>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Heiko Carstens <heiko.carstens@...ibm.com>,
	Chris Mason <clm@...com>, Paul Mackerras <paulus@...ba.org>,
	"H. Peter Anvin" <hpa@...or.com>, Christoph Hellwig <hch@....de>,
	Alasdair Kergon <agk@...hat.com>,
	"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
	Mel Gorman <mgorman@...e.de>,
	Matthew Wilcox <willy@...ux.intel.com>,
	Ross Zwisler <ross.zwisler@...ux.intel.com>,
	Rik van Riel <riel@...hat.com>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	Jens Axboe <axboe@...nel.dk>, Theodore Ts'o <tytso@....edu>,
	"Martin K. Petersen" <martin.petersen@...cle.com>,
	Julia Lawall <Julia.Lawall@...6.fr>, Tejun Heo <tj@...nel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	paulmck@...ux.vnet.ibm.com
Subject: Re: [PATCH v2 00/10] evacuate struct page from the block layer,
 introduce __pfn_t


* Ingo Molnar <mingo@...nel.org> wrote:

> > Is handling kernel pagefault on the vmemmap completely out of the 
> > picture ? So we would carveout a chunck of kernel address space 
> > for those pfn and use it for vmemmap and handle pagefault on it.
> 
> That's pretty clever. The page fault doesn't even have to do remote 
> TLB shootdown, because it only establishes mappings - so it's pretty 
> atomic, a bit like the minor vmalloc() area faults we are doing.
> 
> Some sort of LRA (least recently allocated) scheme could unmap the 
> area in chunks if it's beyond a certain size, to keep a limit on 
> size. Done from the same context and would use remote TLB shootdown.
> 
> The only limitation I can see is that such faults would have to be 
> able to sleep, to do the allocation. So pfn_to_page() could not be 
> used in arbitrary contexts.

So another complication would be that we cannot just unmap such pages 
when we want to recycle them, because the struct page in them might be 
in use - so all struct page uses would have to refcount the underlying 
page. We don't really do that today: code just looks up struct pages 
and assumes they never go away.

Thanks,

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