linux-kernel - Re: Populating multiple ptes at fault time

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]

Message-ID: <33307c790809181421k52ed6a36h9d4ee40d5799a536@mail.gmail.com>
Date:	Thu, 18 Sep 2008 14:21:21 -0700
From:	"Martin Bligh" <mbligh@...gle.com>
To:	"Christoph Lameter" <cl@...ux-foundation.org>
Cc:	"Chris Snook" <csnook@...hat.com>,
	"Jeremy Fitzhardinge" <jeremy@...p.org>,
	"Nick Piggin" <nickpiggin@...oo.com.au>,
	"Hugh Dickens" <hugh@...itas.com>,
	"Linux Memory Management List" <linux-mm@...ck.org>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Avi Kivity" <avi@...ranet.com>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Rik van Riel" <riel@...hat.com>
Subject: Re: Populating multiple ptes at fault time

>>>> Yup, basically you're assuming good locality of reference, but it turns
>>>> out that (as davej would say) "userspace sucks".
>>> Well, *most* userspace sucks.  It might still be worthwhile to do this when
>>> userspace is using madvise().
>>
>> Quite possibly true ... something to benchmark.
>
> Well, I guess we need a new binary format that allows one to execute binaries
> in kernel address space with full powers.

Seems ... extreme ;-)
Maybe we just do it if we're in readahead? (or similar)
--
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/