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: <Pine.LNX.4.64.0704201012500.20723@schroedinger.engr.sgi.com>
Date:	Fri, 20 Apr 2007 10:15:00 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	William Lee Irwin III <wli@...omorphy.com>
cc:	Mel Gorman <mel@...net.ie>, linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Nick Piggin <nickpiggin@...oo.com.au>, Andi Kleen <ak@...e.de>,
	Paul Jackson <pj@....com>, Dave Chinner <dgc@....com>
Subject: Re: [RFC 7/8] Enhance ramfs to support higher order pages

On Fri, 20 Apr 2007, William Lee Irwin III wrote:
> 
> On Fri, Apr 20, 2007 at 09:30:30AM -0700, Christoph Lameter wrote:
> > We can map arbitrary 4k chunks of larger pages.
> 
> The core VM can do that but the hugetlb architectural code can't fall
> back to smaller page sizes. It also should not be put into a situation
> where it needs to do so given the semantics it must honor.

Wel we could potentially add a handle_pmd_fault to the vm...?
 
> Also, the final assertion is inaccurate. Fault handlers must instantiate
> pages of order mapping->order when faulting in a page of a file with
> a given pagecache size. The semantics of faulting and mmap()'ing are

Why? I agree that the page state of the higher order page must be updated 
consistently but one can use a pte to map a 4k chunk of a higher 
order page.


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ